Re: 8.3beta1 testing on Solaris - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 8.3beta1 testing on Solaris
Date
Msg-id 26010.1193345641@sss.pgh.pa.us
Whole thread Raw
In response to 8.3beta1 testing on Solaris  ("Jignesh K. Shah" <J.K.Shah@Sun.COM>)
Responses Re: 8.3beta1 testing on Solaris  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
"Jignesh K. Shah" <J.K.Shah@Sun.COM> writes:
> CLOG data is
> not cached in any PostgreSQL shared memory segments

The above statement is utterly false, so your trace seems to indicate
something broken.  Are you sure these were the only reads of pg_clog
files?  Can you extend the tracing to determine which page of the file
got read?  I am wondering if your (unspecified) test load was managing
to touch more pages of the clog than there is room for in shared memory.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually
Next
From: David Fetter
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually