From: Craig Ringer <craig@postnewspapers.com.au>
To: Marti Raudsepp <marti@juffo.org>
Cc: felix <crucialfelix@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Really really slow select count(*)
Date: Tue, 08 Feb 2011 07:49:27 +0800
Message-ID: <4D508507.8010306@postnewspapers.com.au> (raw)
In-Reply-To: <AANLkTi=TO=pCTgbWfJzHmmtbrY-sWi6nYG2e-5Kyhxdp@mail.gmail.com>
References: <AANLkTinAJcm5A+i1O_R87aiYyu8N2OWgoaL9RfR=tUR9@mail.gmail.com>
<4D4C138C.7010304@2ndquadrant.com>
<4D4C1555.40209@peak6.com>
<AANLkTikrS5JkJDMjAXpcRWRnuLbX+MHB=CWb_mFa9qb-@mail.gmail.com>
<4D4C2AC3.5020804@peak6.com>
<AANLkTin8ndBSU9ZJ2uAdnvYQ7oLBg2S04bqAXn-s5qv+@mail.gmail.com>
<AANLkTim+aLaihKbNSsiiL4exgtCeRqCh_50j48jHFDQm@mail.gmail.com>
<AANLkTimnFc-hKG+PFEfwBPLAoK6q9kx=nc_4Fr++C_QB@mail.gmail.com>
<4D4F6109.1090209@postnewspapers.com.au>
<AANLkTi=TO=pCTgbWfJzHmmtbrY-sWi6nYG2e-5Kyhxdp@mail.gmail.com>
On 02/07/2011 06:30 PM, Marti Raudsepp wrote:
> On Mon, Feb 7, 2011 at 05:03, Craig Ringer<craig@postnewspapers.com.au> wrote:
>> What would possibly help would be if Pg could fall back to lower
>> shared_buffers automatically, screaming about it in the logs but still
>> launching. OTOH, many people don't check the logs, so they'd think their
>> new setting had taken effect and it hadn't - you've traded one usability
>> problem for another. Even if Pg issued WARNING messages to each client
>> that connected, lots of (non-psql) clients don't display them, so many
>> users would never know.
>>
>> Do you have a suggestion about how to do this better? The current
>> approach is known to be rather unlovely, but nobody's come up with a
>> better one that works reasonably and doesn't trample on other System V
>> shared memory users that may exist on the system.
>
> We could do something similar to what Apache does -- provide distros
> with a binary to check the configuration file in advance. This check
> program is launched before the "restart" command, and if it fails, the
> server is not restarted.
That would work for config file errors (and would probably be a good
idea) but won't help with bad shared memory configuration. When Pg is
already running, it's usually not possible for a test program to claim
the amount of shared memory the config file says to allocate, because Pg
is already using it. Nonetheless, Pg will work fine when restarted.
--
Craig Ringer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: craig@postnewspapers.com.au, marti@juffo.org, crucialfelix@gmail.com
Subject: Re: Really really slow select count(*)
In-Reply-To: <4D508507.8010306@postnewspapers.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox