| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | felix <crucialfelix(at)gmail(dot)com> |
| Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Really really slow select count(*) |
| Date: | 2011-02-07 18:42:02 |
| Message-ID: | AANLkTin7WvZAK+yYoJw0KruVG4tuoPW9+nMcfiGEtePV@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Feb 7, 2011 at 8:05 AM, felix <crucialfelix(at)gmail(dot)com> wrote:
> +1
> this is exactly what I was looking for at the time: a -t (configtest)
> option to pg_ctl
> and I think it should fall back to lower shared buffers and log it.
> SHOW ALL; would show the used value
however, much like apache, this might not have gotten caught. In
order to catch it we'd have to see how much shared mem was available,
and I think you have to actually allocate it to find out if you can.
Since pg is already running, allocating shared_buffers / fsm twice
might fail when allocating it once would succeed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-02-07 19:05:25 | Re: Really really slow select count(*) |
| Previous Message | Greg Smith | 2011-02-07 16:03:42 | Re: [PERFORM] pgbench to the MAXINT |