Re: Log full with gigabyes of CurTransactionContex - Mailing list pgsql-admin

From Michael Monnerie
Subject Re: Log full with gigabyes of CurTransactionContex
Date
Msg-id 200906152218.54626@zmi.at
Whole thread Raw
In response to Re: Log full with gigabyes of CurTransactionContex  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Log full with gigabyes of CurTransactionContex  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-admin by date:

Previous
From: "Hapase, Pranjali"
Date:
Subject: Regarding PostgreSQL problem.
Next
From: Igor Polishchuk
Date:
Subject: Is IDLE session really idle?