On Tue, Jan 31, 2012 at 2:36 PM, Marc Mamin wrote:
> But this raises an interesting question on how/where does Postgres store
> statistics on functional indexes.
> in pg_statistics there are information on the column content, but I couldn't
> find stats on the function result which is fully comp
On Tue, Jan 31, 2012 at 1:20 PM, Merlin Moncure wrote:
> yeah -- postgresql.conf settings are not going to play a big role here unless:
> *) you defer index build to the end of the load, and do CREATE INDEX
> and crank maintenance_work_mem
> *) you are doing lots of transactions and relax your syn
Saurabh wrote:
> wal_buffers = 5MB
As as already been suggested, use 16MB (or if the version you're
using supports it, the default of -1);
> autovacuum = off
If the only activity while this is off is a bulk load, that might be
OK, but be sure *not* to leave this off. You will almost certa
2012/1/22 Tomas Vondra :
> That's suspiciously similar to the checkpoint timeout (which was set to
> 4 minutes), but why should this matter for minimal WAL level and not for
> archive?
I went through and looked at all the places where we invoke
XLogIsNeeded(). When XLogIsNeeded(), we:
1. WAL log
On Fri, Dec 16, 2011 at 1:27 PM, Greg Smith wrote:
> Forwarding this on from someone who may pop up on the list too. This is a
> new server that's running a query slowly. The rate at which new semops
> happen may be related. OS is standard RHEL 5.5, kernel 2.6.18-194.32.1.el5.
> One possibly i
On 31/01/2012 09:07, CSS wrote:
Hello all,
Just wanted to share some results from some very basic benchmarking
runs comparing three disk configurations on the same hardware:
http://morefoo.com/bench.html
That's great!
*Tyan B7016 mainboard w/onboard LSI SAS controller
*2x4 core xeon E5506 (
