From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "devrim(at)gunduz(dot)org" <devrim(at)gunduz(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |
Date: | 2012-09-17 13:58:37 |
Message-ID: | 234.1347890317@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> Btw, I played with this some more on Saturday and I think, while definitely a
> bad bug, the actual consequences aren't as bad as at least I initially feared.
> Fake relcache entries are currently set in 3 scenarios during recovery:
> 1. removal of ALL_VISIBLE in heapam.c
> 2. incomplete splits and incomplete deletions in nbtxlog.c
> 3. incomplete splits in ginxlog.c
> [ #1 doesn't really hurt in 9.1, and the others are low probability ]
OK, that explains why we've not seen a blizzard of trouble reports.
Still seems like a good idea to fix it ASAP, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-09-17 14:59:06 | Re: [COMMITTERS] pgsql: Fix bufmgr so CHECKPOINT_END_OF_RECOVERY behaves as a shutdown c |
Previous Message | Simon Riggs | 2012-09-17 08:44:39 | Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-09-17 14:08:01 | Re: [PATCH 3/8] Add support for a generic wal reading facility dubbed XLogReader |
Previous Message | Gurjeet Singh | 2012-09-17 13:49:17 | Re: Patch to include c.h |