up by quotes or backslashes in words that are being matched to database
names (per gripe from Ian Barwick, though I didn't use his patch).
Also fix possible memory leakage if _complete_with_query isn't run to
completion (not clear if that can happen or not, but be safe).

it.  Not sure why I'd thought it would be a good idea to do differently
way back when, but Greg Stark exposed the folly of doing so ...

little use.

be made, to avoid corner cases where max_connections ends up unreasonably
small because shared_buffers is hogging too much shmem space.  Per pghackers
discussion about a week ago.  Also, fix the copy-newlines problem in a
more robust way, by using COPY FROM filename instead of COPY FROM STDIN;
per a suggestion from Peter.

when the pg_class.relhassubclass value is already correct.  This should
avoid most cases of the 'tuple concurrently updated' problem that
Robert Creager recently complained about.  Also remove a bunch of dead
code in StoreCatalogInheritance() --- it was still computing the complete
list of direct and indirect inheritance ancestors, though that list has
not been needed since we got rid of the pg_ipl catalog.

rather than allocating them on the stack.

Fixes complaint from gcc 3.3.1.

already check for alignment.

when -fstrict-aliasing is turned on, as it is in the latest gcc when you
use -O2

Andrew Dunstan

Change conditionals to be more constent with our code

if (const == var) => if (var == const).

Manfred Koizar

Viktor Vislobokov

> * Prevent libpq's PQfnumber() from lowercasing the column name
572d572
< * Vadim is Vadim B. Mikheev <vadim4o@email.com> of Sector Data

> only think to look at sort_mem if they already had a clue.  It should
> be mentioned under bulk data load (in performance tips chapter)

Attached is a doc patch that does this. The way I've worded it may not
be the best, though.

Neil Conway

>   to allow fast COUNT(*) queries with no WHERE clause(?) [count]

Andrew Dunstan

> 	o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]

> * Have VACUUM FULL use REINDEX rather than index vacuum

About section 8.5.1.5. ("Special Values"):

I suggest adding LOCALTIMESTAMP and LOCALTIME to the first paragraph.
Maybe it should be phrased as:

  The following SQL-compatible functions can be used to obtain
  current datetime-related values: CURRENT_DATE, CURRENT_TIME,
  CURRENT_TIMESTAMP, LOCALTIME and LOCALTIMESTAMP.
  (See Section 9.8.4.)

Troels Arvin

misscanning of this construct:

SELECT ''hello world''
-- SELECT ''goodbye world''
::text;