Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] 8.3beta1 testing on Solaris

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM>
Cc: pgsql-performance(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] 8.3beta1 testing on Solaris
Date: 2007-10-25 20:54:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-performance
"Jignesh K. Shah" <J(dot)K(dot)Shah(at)Sun(dot)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

In response to


pgsql-performance by date

Next:From: Gregory StarkDate: 2007-10-25 22:37:33
Subject: Re: 8.3beta1 testing on Solaris
Previous:From: Chris BrowneDate: 2007-10-25 20:46:46
Subject: Re: Bunching "transactions"

pgsql-hackers by date

Next:From: David FetterDate: 2007-10-25 21:04:58
Subject: Re: [HACKERS] Re: pgsql: Extract catalog info for errorreporting before an error actually
Previous:From: Stefan KaltenbrunnerDate: 2007-10-25 20:28:54
Subject: Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group