postgresql.git, branch REL7_2_STABLE This is the main PostgreSQL git repository. http://git.postgresql.org/cgit/postgresql.git/atom?h=REL7_2_STABLE 2005-08-16T03:33:39Z Remove registration message in all the supported back branches; 2005-08-16T03:33:39Z Tom Lane 2005-08-16T03:33:39Z urn:sha1:f47f4be902a7ef01b8e340b790f37e4703289501 we had decided to drop it for 7.4, and no one misses it. MemSet() must not cast its pointer argument to int32* until after it has 2005-07-18T15:55:01Z Tom Lane 2005-07-18T15:55:01Z urn:sha1:a55a75f02dd83761d201030e11277ebbba27a1bc checked that the pointer is actually word-aligned. Casting a non-aligned pointer to int32* is technically illegal per the C spec, and some recent versions of gcc actually generate bad code for the memset() when given such a pointer. Per report from Andrew Morrow. Back-patch into 7.2 branch the 7.3 changes that made contrib/seg 2005-07-16T19:48:16Z Tom Lane 2005-07-16T19:48:16Z urn:sha1:84e5ce7eb9c193586cca94a3de771c3188fd708e error messages reasonably independent of the bison version used to build segparse.c. Needed to get this branch passing on buildfarm. Back-patch into 7.2 branch the 7.3 changes that made contrib/cube 2005-07-16T19:27:20Z Tom Lane 2005-07-16T19:27:20Z urn:sha1:44e7a2ae609d0cbae8ae01ebc03c02b96cacb002 error messages reasonably independent of the bison version used to build cubeparse.c. Needed to get this branch passing on buildfarm. Mark the geometry regression test as an ignorable failure in the pre-7.4 2005-07-16T19:02:01Z Tom Lane 2005-07-16T19:02:01Z urn:sha1:861e3c7a07c5deb8ff2d67e439381516407ffd59 branches. Per discussion, this seems saner than trying to maintain last-significant-digit regression test outputs for all supported platforms. Fix bogus "extern int errno;" in back branches, per Andrew Dunstan. 2005-07-16T15:24:08Z Tom Lane 2005-07-16T15:24:08Z urn:sha1:c969e30d7d7133f703d44f65e173052a9a259d97 Make libpq_gettext save and restore errno in a Windows-compatible way. 2005-07-08T15:25:46Z Tom Lane 2005-07-08T15:25:46Z urn:sha1:91d381e3c01062f506ea947891d9f257cfe207f6 Also, back-patch fix into back branches. plpgsql's exec_assign_value() freed the old value of a variable before 2005-06-20T20:45:12Z Tom Lane 2005-06-20T20:45:12Z urn:sha1:224501ed68f912981295cc8c1dfecd3d175c9db5 copying/converting the new value, which meant that it failed badly on "var := var" if var is of pass-by-reference type. Fix this and a similar hazard in exec_move_row(); not sure that the latter can manifest before 8.0, but patch it all the way back anyway. Per report from Dave Chapeskie. The random selection in function linear() could deliver a value equal to max 2005-06-14T14:21:43Z Tom Lane 2005-06-14T14:21:43Z urn:sha1:2b91c8cf007e1008f7d6ccc9813908d30af8b4c0 if geqo_rand() returns exactly 1.0, resulting in failure due to indexing off the end of the pool array. Also, since this is using inexact float math, it seems wise to guard against roundoff error producing values slightly outside the expected range. Per report from bug@zedware.org. Add test to WAL replay to verify that xl_prev points back to the previous 2005-05-31T19:11:28Z Tom Lane 2005-05-31T19:11:28Z urn:sha1:e4ce3e76ce300e9e732c511c9b3e9bf98d02fd9c 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.