delta/postgresql.git, branch REL8_3_22

Stamp 8.3.22.

2012-12-03T20:28:41+00:00

Update release notes for 9.2.2, 9.1.7, 9.0.11, 8.4.15, 8.3.22.

2012-12-03T20:10:27+00:00

Fix documentation of path(polygon) function.

2012-12-03T16:09:16+00:00

Obviously, this returns type "path", but somebody made a copy-and-pasteo
long ago.

Dagfinn Ilmari Mannsåker

Translation updates

2012-12-03T12:50:43+00:00

Update time zone data files to tzdata release 2012j.

2012-12-02T21:37:07+00:00

DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa,
and portions of Brazil.

Fix psql crash while parsing SQL file whose encoding is different from

2012-12-02T12:23:51+00:00

client encoding and the client encoding is not *safe* one. Such an
example is, file encoding is UTF-8 and client encoding SJIS. Patch
contributed by Jiang Guiqing.

Prevent passing gmake's environment variables down through pg_regress.

2012-12-01T22:24:15+00:00

When we do "make install" to create a temp installation, we don't want
that instance of make to try to communicate with any instance of make
that might be calling us.  This is known to cause problems if the
upper make has a -jN flag, and in principle could cause problems even
without that.  Unset the relevant environment variables to prevent such
issues.

Andres Freund

Take buffer lock while inspecting btree index pages in contrib/pageinspect.

2012-11-30T22:02:53+00:00

It's not safe to examine a shared buffer without any lock.

Add missing buffer lock acquisition in GetTupleForTrigger().

2012-11-30T18:56:24+00:00

If we had not been holding buffer pin continuously since the tuple was
initially fetched by the UPDATE or DELETE query, it would be possible for
VACUUM or a page-prune operation to move the tuple while we're trying to
copy it.  This would result in a garbage "old" tuple value being passed to
an AFTER ROW UPDATE or AFTER ROW DELETE trigger.  The preconditions for
this are somewhat improbable, and the timing constraints are very tight;
so it's not so surprising that this hasn't been reported from the field,
even though the bug has been there a long time.

Problem found by Andres Freund.  Back-patch to all active branches.

Produce a more useful error message for over-length Unix socket paths.

2012-11-30T00:57:38+00:00

The length of a socket path name is constrained by the size of struct
sockaddr_un, and there's not a lot we can do about it since that is a
kernel API.  However, it would be a good thing if we produced an
intelligible error message when the user specifies a socket path that's too
long --- and getaddrinfo's standard API is too impoverished to do this in
the natural way.  So insert explicit tests at the places where we construct
a socket path name.  Now you'll get an error that makes sense and even
tells you what the limit is, rather than something generic like
"Non-recoverable failure in name resolution".

Per trouble report from Jeremy Drake and a fix idea from Andrew Dunstan.