delta/postgresql.git, branch REL8_3_6

Fix plpgsql to not treat INSERT INTO as an INTO-variables clause anywhere

2009-02-02T20:25:43+00:00

in the string, not just at the start.  Per bug #4629 from Martin Blazek.

Back-patch to 8.2; prior versions don't have the problem, at least not in
the reported case, because they don't try to recognize INTO in non-SELECT
statements.  (IOW, this is really fallout from the RETURNING patch.)

Defend against null input in analyze_requires_snapshot(), per report

2009-01-30T16:59:10+00:00

from Rushabh Lathia.

Back-patch of patch of 2009-01-08.  This is necessary in 8.3, as reported
by Bjorn Munch.  It's not currently necessary in 8.2, AFAICS, but seems
best to include it there too.

tag for 8.3.6

2009-01-30T02:59:29+00:00

Update back-branch release notes.

2009-01-30T00:37:42+00:00

Translation updates

2009-01-29T22:07:53+00:00

Update time zone data files to tzdata release 2009a: introduces Asia/Kathmandu

2009-01-29T20:00:07+00:00

as the preferred spelling of that zone name, corrects historical DST
information for Switzerland and Cuba.

Replace argument-checking Asserts with regular test-and-elog checks in all

2009-01-29T19:23:58+00:00

encoding conversion functions.  These are not can't-happen cases because
it's possible to create a conversion with the wrong conversion function
for the specified encoding pair.  That would lead to an Assert crash in
an Assert-enabled build, or incorrect conversion otherwise, neither of
which is desirable.  This would be a DOS issue if production databases
were customarily built with asserts enabled, but fortunately that's not so.
Per an observation by Heikki.

Back-patch to all supported branches.

Fix incorrect dereferencing of char* to array's index.

2009-01-29T16:09:12+00:00

Per Tommy Gildseth  report

Fix bug with multiple evaluation of tsearch2 compatibility trigger, trigger

2009-01-28T18:32:55+00:00

data should be restored.
Backpatch only for 8.3 because previous versions haven't such layer.

Go over all OpenSSL return values and make sure we compare them

2009-01-28T15:06:57+00:00

to the documented API value. The previous code got it right as
it's implemented, but accepted too much/too little compared to
the API documentation.

Per comment from Zdenek Kotala.