to create a TCP/IP socket from FATAL to LOG.  This was unwise;
historically we have expected socket conflicts to abort postmaster
startup.  Conflicts on port numbers with another postmaster can only
be detected reliably at the TCP socket level.

to bypass the error, --without-spinlocks.

from Mark Kirkwood.  Also show the sample size.

the others in style.

makes a few more small improvements to runtime.sgml, and makes some SGML
conventions more consistent.

Neil Conway

> keywords for clarity.

Yeah, this is basically what I meant, sorry I didn't get to it quicker.

However, I tested it out a little and the patch you made doesn't work
because it produces commands like:

VACUUM ANALYZE "public.FooBar"

Which doesn't work, so I made my own patch that creates commands like:

VACUUM ANALYZE "public"."FooBar"

This allows for mixed case schema names as well as tables.

Adam, can you please give this a test as you are the person who caught
the bug in the first place.

Thanks,

Matthew T. O'Connor

<varname> conventions more consistent, and improve the ANALYZE ref page.

Neil Conway

documentation.

Neil Conway

Christopher Kings-Lynne

ALTER TABLE mytable drop column last_column_of_table;

the timetravel trigger say on UPDATE/DELETE:

ERROR:  parser: parse error at end of input


Here is the patch for this bug

B?jthe Zolt?n

some examples of the new syntax and a reference to the documentation.

Joe Conway.

Robert Treat

per recent discussions.

> * Issue NOTICE if foreign key data type doesn't match primary key

> * Have EXPLAIN ANALYZE highlight poor optimizer estimates

Neil Conway

ERROR to WARNING so we keep control.

isn't loaded into the database.

Matthew T. O'Connor.

UnixWare.

Larry Rosenman

> * Have pg_dump -c clear the database using dependency information

feature they complain about isn't a feature or cannot be implemented without
definitional changes.

discussion.  (Still have some work to do editing the remainder.)