| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Frank Joerdens <frank(at)joerdens(dot)de> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Nic Ferrier <nic(at)woome(dot)com>, Avleen Vig <avleen(at)woome(dot)com>, Mike Rogers <mike(dot)rogers(at)woome(dot)com> |
| Subject: | Re: Full statement logging problematic on larger machines? |
| Date: | 2009-03-11 20:46:10 |
| Message-ID: | 3401.1236804370@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Frank Joerdens <frank(at)joerdens(dot)de> writes:
> Greetings. We're having trouble with full logging since we moved from
> an 8-core server with 16 GB memory to a machine with double that
> spec and I am wondering if this *should* be working or if there is a
> point on larger machines where logging and scheduling seeks of
> background writes - or something along those lines; it might be a
> theory - doesn't work together any more?
You didn't tell us anything interesting about *how* you are logging,
so it's hard to comment on this. Are you just writing to stderr?
syslog? using PG's built-in log capture process? It would be good
to show all of your log-related postgresql.conf settings.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jignesh K. Shah | 2009-03-11 20:53:49 | Proposal of tunable fix for scalability of 8.4 |
| Previous Message | Scott Carey | 2009-03-11 20:31:13 | Re: random_page_cost vs ssd? |