Tom Lane wrote:
Josh Berkus <[EMAIL PROTECTED]> writes:
Oh, and wal_buffers, the default for which we should just change if it
weren't for SHMMAX.
Uh, why? On a workload of mostly small transactions, what value is
there in lots of wal_buffers?
Actually, it's also useful for any workload with many connections. Any
time you have high throughput, really. We've seen this on DBT2,
SpecJAppserver and iGen.
--Josh
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
