| 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: | 26010.1193345641@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2007-10-25 21:04:58 | Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually |
| Previous Message | Stefan Kaltenbrunner | 2007-10-25 20:28:54 | Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-10-25 22:37:33 | Re: 8.3beta1 testing on Solaris |
| Previous Message | Chris Browne | 2007-10-25 20:46:46 | Re: Bunching "transactions" |