Thread: Coming soon: PG 7.4.4, 7.3.7, 7.2.5
The core committee has agreed that this bug http://archives.postgresql.org/pgsql-hackers/2004-08/msg00639.php is serious enough that we'd better push out update releases for all the affected versions. I want to hold off a day or so and see if a couple of currently-open bug reports can be resolved, but it's going to happen soon. If anyone has any back-patches that they've been thinking of getting in, now would be a good time. BTW, I realized this morning that 7.1.* also has a version of the bug, because it too writes and flushes an XLOG COMMIT record before it does anything about marking the transaction complete in pg_log. So it likewise would have the problem that a checkpoint occurring just after the COMMIT might not include the pg_log update, leading to possible loss of the pg_log update in event of crash and replay from that checkpoint. Core's feeling is that we will not try to backpatch 7.1. The patch used for the later versions will not apply to 7.1 because it doesn't have LWLocks, so some nontrivial effort would be needed to develop a fix. Given the age of that release, and the other serious problems it has (the transaction-ID-wraparound problem for one), it's time to officially state that it is broken and unsupportable. Comments anyone? Backpatches for other bugs? regards, tom lane
On Wed, Aug 11, 2004 at 06:08:10PM -0400, Tom Lane wrote: > The core committee has agreed that this bug > http://archives.postgresql.org/pgsql-hackers/2004-08/msg00639.php is > serious enough that we'd better push out update releases for all the > affected versions. I want to hold off a day or so and see if a > couple of currently-open bug reports can be resolved, but it's going > to happen soon. If anyone has any back-patches that they've been > thinking of getting in, now would be a good time. Are the packaged versions (OK, the Dea^WRed Hat RPMs) going out at the same time? On a slightly related topic, I'm thinking I should only put the latest, greatest on the bt server, but if others think otherwise, I'd be happy to put up more. Cheers, D -- David Fetter david@fetter.org http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote!
David Fetter <david@fetter.org> writes:
> Are the packaged versions (OK, the Dea^WRed Hat RPMs) going out at the
> same time?
No, but I'll be working on those as soon as the tarballs are wrapped.
> On a slightly related topic, I'm thinking I should only put the
> latest, greatest on the bt server, but if others think otherwise, I'd
> be happy to put up more.
The 8.0 beta and the latest stable (7.4.3, soon 7.4.4) would seem
sufficient to me, but maybe you should ask this on -general.
regards, tom lane
The pg_dump fix in 8.0 that stops the destruction of existing users in the target database via "DELETE FROM pg_shadow WHERE usesysid <> (..." would be great! regards Mark Tom Lane wrote: >Comments anyone? Backpatches for other bugs? > > >
Sorry - I meant pg_dump*all* rather than pg_dump. Mark Kirkwood wrote: > The pg_dump fix in 8.0 that stops the destruction of existing users in > the target database via "DELETE FROM pg_shadow WHERE usesysid <> (..." > would be great! > > regards > > Mark > > Tom Lane wrote: > >> Comments anyone? Backpatches for other bugs? >> >> >> >