recreated since the start of our transaction, our first reference to it
errored out because we'd try to reuse our old relcache entry for it.
Do this by accepting SI inval messages just before relcache search in
heap_openr, so that dead relcache entries will be flushed before we
search.  Also, break heap_open/openr into two pairs of routines,
relation_open(r) and heap_open(r).  The relation_open routines make
no tests on relkind and so can be used to open anything that has a
pg_class entry.  The heap_open routines are wrappers that add a relkind
test to preserve their established behavior.  Use the relation_open
routines in several places that had various kluge solutions for opening
rels that might be either heap or index rels.

Also, remove the old 'heap stats' code that's been superseded by Jan's
stats collector, and clean up some inconsistencies in error reporting
between the different types of ALTER TABLE.

stored in pg_pwd, to guard against failures of the sort observed by
Tom Yackel.  Note: in the case of encrypted passwords this is no
restriction, since the string we are interested in is the MD5 hash.

index usage.

element content.

message spacing.

which incorporates recent changes by Bruce to
readability of some messages and few more translations.

--
Serguei A. Mokhov

Zhenbang Wei

information about nulls and sort order.

This is based on information obtained from Peter Eisentraut and
Tom Lane on pgsql-hackers.

Please check my English and Docbook markup, as both are a second
language to me.

Rene Pijlman

Add space between slash for ALTER TABLE / ADD ....

Regression and *.po updates to follow.

Zhenbang Wei

forth@pagic.net

Results checked by Olivier Prenant.

from Philip Warner.  Side effect of change is that GROUP BY expressions
will not be re-evaluated at multiple plan levels anymore, whereas this
sometimes happened with old code.

fixed change in behavior introduced in bytea / getBytes changes.  This patch reverts back unintentional change in behavior to return raw value even when not bytea column

updated patch from Mark Lillywhite per Tom Lane's comments: subtract VARHDRSZ first then and with 0xffff

applied patch from Mark Lillywhite, patch was already applied to jdbc2, this applies same fix to jdbc1 code