Robert Haas writes:
> On Thu, Apr 2, 2015 at 3:59 PM, Tom Lane wrote:
>> Perhaps the difference has to do with whether pg_am's pg_class tuple is
>> on a page that hasn't got enough room for a HOT update? But I definitely
>> tried it several times and consistently got the same failure before.
>
On Thu, Apr 2, 2015 at 3:59 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Apr 2, 2015 at 2:55 PM, Tom Lane wrote:
>>> Actually, now that I think it through, the "could not open relation"
>>> error is pretty odd in itself. If we are trying to open pg_am using
>>> a stale catalog snapshot,
Robert Haas writes:
> On Thu, Apr 2, 2015 at 2:55 PM, Tom Lane wrote:
>> Actually, now that I think it through, the "could not open relation"
>> error is pretty odd in itself. If we are trying to open pg_am using
>> a stale catalog snapshot, it seems like we ought to reliably find its
>> old pg_
On Thu, Apr 2, 2015 at 2:55 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Apr 2, 2015 at 2:40 PM, Tom Lane wrote:
>>> However, I'm having second thoughts about whether we've fully diagnosed
>>> this. Three out of the four failures we've seen in the buildfarm reported
>>> "cache lookup fa
Robert Haas writes:
> On Thu, Apr 2, 2015 at 2:40 PM, Tom Lane wrote:
>> However, I'm having second thoughts about whether we've fully diagnosed
>> this. Three out of the four failures we've seen in the buildfarm reported
>> "cache lookup failed for access method 403", not "could not open relati
On Thu, Apr 2, 2015 at 2:40 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Apr 2, 2015 at 12:54 PM, Tom Lane wrote:
>>> It looks to me like an appropriate fix would be as attached; thoughts?
>
>> Hmm, that fix doesn't reach as far as what I did. My proposal would
>> regard a catalog snaps
Robert Haas writes:
> On Thu, Apr 2, 2015 at 12:54 PM, Tom Lane wrote:
>> It looks to me like an appropriate fix would be as attached; thoughts?
> Hmm, that fix doesn't reach as far as what I did. My proposal would
> regard a catalog snapshot as immediately stale, so if we're asked for
> a cata
On Thu, Apr 2, 2015 at 12:54 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Wed, Apr 1, 2015 at 7:05 PM, Tom Lane wrote:
>>> I've not fully tracked it down, but I think that the blame falls on the
>>> MVCC-snapshots-for-catalog-scans patch; it appears that it's trying to
>>> read pg_am's pg_cla
Robert Haas writes:
> On Wed, Apr 1, 2015 at 7:05 PM, Tom Lane wrote:
>> I've not fully tracked it down, but I think that the blame falls on the
>> MVCC-snapshots-for-catalog-scans patch; it appears that it's trying to
>> read pg_am's pg_class entry with a snapshot that's too old, possibly
>> bec
On Wed, Apr 1, 2015 at 7:05 PM, Tom Lane wrote:
> I've been able to reproduce this. The triggering event seems to be that
> the "VACUUM FULL pg_am" in vacuum.sql has to happen while another backend
> is starting up. With a ten-second delay inserted at the bottom of
> PerformAuthentication(), it'
I wrote:
> Observe these recent buildfarm failures:
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mule&dt=2015-03-21%2000%3A30%3A02
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=guaibasaurus&dt=2015-03-23%2004%3A17%3A01
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=
Observe these recent buildfarm failures:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mule&dt=2015-03-21%2000%3A30%3A02
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=guaibasaurus&dt=2015-03-23%2004%3A17%3A01
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mule&dt=2015-03-
12 matches
Mail list logo
