RTE of interest, rather than the whole rangetable list.  This makes
the API more understandable and avoids duplicate RTE lookups.  This
patch reverts no-longer-needed portions of my patch of 2004-08-19.

> * Allow pg_ctl to work properly with configuration files located outside
>   the PGDATA directory
>
>   pg_ctl can not read the pid file because it isn't located in the
>   config directory but in the PGDATA directory.  The solution is to
>   allow pg_ctl to read and understand postgresql.conf to find the
>   data_directory value.
>

>
>   O_DIRECT doesn't have the same media write guarantees as fsync, so it
>   is in addition to the fsync method, not in place of it.
>

Division rounding was causing incorrect results.  Test case:

	test=> SELECT 12345678901234567890 % 123;
	 ?column?
	----------
	       78
	(1 row)

Was returning -45.

Weiping (Laser)

accordingly (this field was always initialized to true). Patch from
Alvaro Herrera.

performance problem pointed out by phil@vodafone: to wit, we were
spending O(N^2) time to check dropped-ness in an N-deep join tree,
even in the case where the tree was freshly constructed and couldn't
possibly mention any dropped columns.  Instead of recursing in
get_rte_attribute_is_dropped(), change the data structure definition:
the joinaliasvars list of a JOIN RTE must have a NULL Const instead
of a Var at any position that references a now-dropped column.  This
costs nothing during normal parse-rewrite-plan path, and instead we
have a linear-time update to make when loading a stored rule that
might contain now-dropped columns.  While at it, move the responsibility
for acquring locks on relations referenced by rules into this separate
function (which I therefore chose to call AcquireRewriteLocks).
This saves effort --- namely, duplicated lock grabs in parser and rewriter
--- in the normal path at a cost of one extra non-locked heap_open()
in the stored-rule path; seems a good tradeoff.  A fringe benefit is
that it is now *much* clearer that we acquire lock on relations referenced
in rules before we make any rewriter decisions based on their properties.
(I don't know of any bug of that ilk, but it wasn't exactly clear before.)

< * -Compress WAL entries [wal]

no part of the planner did CHECK_FOR_INTERRUPTS().  Add one in a
suitably strategic spot.

Viktor Vislobokov

> * -Compress WAL entries [wal]

> * -Change WAL to use 32-bit CRC, for performance reasons

to just around the bare recv() call that gets a command from the client.
The former placement in PostgresMain was unsafe because the intermediate
processing layers (especially SSL) use facilities such as malloc that are
not necessarily re-entrant.  Per report from counterstorm.com.

broke it.  Maybe we do need an automated check ...

- Added patch by Gavin Scott <gavin@planetacetech.com> for Intel 64bit hardware.

Instead of a separate CRC on each backup block, include backup blocks
in their parent WAL record's CRC; this is important to ensure that the
backup block really goes with the WAL record, ie there was not a page
tear right at the start of the backup block.  Implement a simple form
of compression of backup blocks: drop any run of zeroes starting at
pd_lower, so as not to store the unused 'hole' that commonly exists in
PG heap and index pages.  Tweak PageRepairFragmentation and related
routines to ensure they keep the unused space zeroed, so that the above
compression method remains effective.  All per recent discussions.

< 	o Allow COPY to understand \x as a hex byte
> 	o -Allow COPY to understand \x as a hex byte

supported.  This follows the C standard escapes.

Sergey Ten

and DDL statements.

Backpatch fix to 8.0.X.

Per report from Murthy Kambhampaty

expressions it constructed, causing scalarineqsel to become confused
if the underlying variable was of a domain type.  Per report from
Kevin Grittner.

WAL record; this is necessary to be sure we recognize stale WAL records
when a WAL page was only partially written during a system crash.

Robert Treat

that the parser now can, so that it can reverse-list cases involving
FieldSelect from a RECORD Var.

it can handle cases like (foo.x).y where foo is a subquery and x is
a function-returning-RECORD RTE in that subquery.

for efficiency's sake.  Mark Kirkwood.

and RelationNameGetTupleDesc() as deprecated; remove uses of the
latter in the contrib library.  Along the way, clean up crosstab()
code and documentation a little.

< * Prevent child tables from altering constraints like CHECK that were
<   inherited from the parent table
470a469,471
>
> 	o Prevent child tables from altering constraints like CHECK that were
> 	  inherited from the parent table

> * Prevent child tables from altering constraints like CHECK that were
>   inherited from the parent table

physical-tlist optimization can be applied to FunctionScan nodes as well
as regular tables and SubqueryScans.

hex/decimal/octal.  Documentation already updated.

BACKWARD COMPATIBLE CHANGE