| From: | Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Log full with gigabyes of CurTransactionContex |
| Date: | 2009-06-15 20:18:54 |
| Message-ID: | 200906152218.54626@zmi.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Montag 15 Juni 2009 Tom Lane wrote:
> These two settings are probably the cause. With shared_buffers at
> 2GB, you do not have anywhere near 1GB to play around with in a
> 32-bit environment. Try something like 200M and 500M.
Wouldn't a recommendation to switch to 64bit PostgreSQL be a good idea
also? Maybe his servers can't do that, I don't know.
Also, I've heard that using shared_buffers = 500MB is enough (even in
64bit), and the rest will be cached by Linux cache alone. Is that true?
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-06-15 20:25:50 | Re: Pgsql remote connection issue was: Regarding PostgreSQL problem. |
| Previous Message | Igor Polishchuk | 2009-06-15 20:15:30 | Is IDLE session really idle? |