Re: page corruption on 8.3+ that makes it to standby
От | Robert Haas |
---|---|
Тема | Re: page corruption on 8.3+ that makes it to standby |
Дата | |
Msg-id | AANLkTik6UGBGq_rJ1QF2keYQ2N3S5FfYWmsLGf7A=u4U@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: page corruption on 8.3+ that makes it to standby (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Thu, Jul 29, 2010 at 11:09 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> Here's a version of Jeff's fix1 patch (with a trivial change to the >> comment) that applies to HEAD, REL9_0_STABLE, REL8_4_STABLE, and >> REL8_3_STABLE; a slightly modified version that applies to >> REL8_2_STABLE; and another slightly modified version that applies to >> REL8_1_STABLE and REL8_0_STABLE. REL7_4_STABLE doesn't have >> tablespaces, so the problem can't manifest there, I think. > > Looks sane to the eyeball. I'm not sure if the oldest versions have the > same page-read-time header sanity checks that we have now, so it may be > that there is not a need for this patch all the way back; but it can't > hurt anything. It looks like they do. I am able to reproduce the problem even on 8.0, and the patch does fix it. >> I'm currently compiling and testing all of these. When that's done, >> should I go ahead and check this in, or wait until after beta4 wraps? > > Go ahead and commit, please. Done. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: