From: | Joachim Wieland <joe(at)mcknight(dot)de> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: cluster test |
Date: | 2007-05-26 11:40:27 |
Message-ID: | 20070526114027.GA12075@mcknight.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Sat, May 26, 2007 at 11:40:52AM +0100, Heikki Linnakangas wrote:
> >But we've got plenty of both in the buildfarm, and none of them are
> >showing this failure. So I'm curious to know what's really different
> >about Joachim's installation. It seems he must have a pg_constraint
> >table enough larger than "normal" to discourage the seqscan, but where
> >did that come from? There's only one row in pg_constraint in standard
> >template0 --- could he be working with a custom system that has many
> >more?
> Or maybe some non-default values in postgresql.conf? Like random_page_cost?
No, I use what initdb creates:
$ cat postgresql.conf | grep ^[a-zA-Z]
max_connections = 100 # (change requires restart)
shared_buffers = 24MB # min 128kB or max_connections*16kB
max_fsm_pages = 153600 # min max_fsm_relations*16, 6 bytes each
datestyle = 'iso, dmy'
lc_messages = 'es_ES(at)euro' # locale for system error message
lc_monetary = 'es_ES(at)euro' # locale for monetary formatting
lc_numeric = 'es_ES(at)euro' # locale for number formatting
lc_time = 'es_ES(at)euro' # locale for time formatting
Joachim
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-26 16:14:14 | Re: cluster test |
Previous Message | Heikki Linnakangas | 2007-05-26 10:40:52 | Re: cluster test |