they do not prevent the postmaster from deleting the shmem segment during
a post-backend-crash restart cycle.  Per recent discussion.

else it cannot be used to handle failures detected during WAL replay.
Fortunately this flag isn't actually enforced yet, but get it right.

> * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
>   by searching for non-conflicting constraint names, and prefix with table name

like the next higher one.

regression=# select 1 from tenk1 ta cross join tenk1 tb for update;
ERROR:  no relation entry for relid 3

7.3 said "SELECT FOR UPDATE cannot be applied to a join", which was better
but still wrong, considering that 7.2 took the query just fine.  Fix by
making transformForUpdate() ignore JOIN and other special RTE types,
rather than trying to mark them FOR UPDATE.  The actual error message now
only appears if you explicitly name the join in FOR UPDATE.

proper place, namely the syntax discussion of value expressions.

have included a few fixes over the years to make them more robust and
faster.

patch for rs.previous and test case as well as patch for allowing server and port to be specified in test cases

tag it Release Candidate 1, as previously discussed

platform-dependent results, as per example from Larry Rosenman.

limit on the number of simultaneous connections.  Andrew Dunstan, with
review by Tom Lane.