From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jignesh K. Shah <J.K.Shah@Sun.COM>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3beta1 testing on Solaris
Date: Thu, 25 Oct 2007 16:54:01 -0400
Message-ID: <26010.1193345641@sss.pgh.pa.us> (raw)
In-Reply-To: <4720FB72.8060800@sun.com>
References: <4720FB72.8060800@sun.com>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, J.K.Shah@Sun.COM, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3beta1 testing on Solaris
In-Reply-To: <26010.1193345641@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox