On Mon, Feb 7, 2011 at 8:05 AM, felix <crucialfelix@xxxxxxxxx> 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. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
