From: Natalie Wenz <nataliewenz@ebureau.com>
To: bricklen <bricklen@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Dumping a database that is not accepting commands?
Date: Tue, 17 Sep 2013 14:19:17 -0500
Message-ID: <2EE7C659-6FA5-409D-8401-3F8A22E9DF3A@ebureau.com> (raw)
In-Reply-To: <CAGrpgQ9TgYirUTDe6v1i_sat0j0aaAXy48nqP6cANKWAM5nqNg@mail.gmail.com>
References: <B150080B-9E9A-456F-8B8D-110F07621165@ebureau.com>
<1379421830.30619.YahooMailNeo@web162902.mail.bf1.yahoo.com>
<A8C537BF-969B-41B9-8CFC-652F63E95F57@ebureau.com>
<CAGrpgQ9TgYirUTDe6v1i_sat0j0aaAXy48nqP6cANKWAM5nqNg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
No… the shared_buffers value is just a legacy value that never got changed (the shmmax value in sysctl is still 1073741824). When I set up the new database, I set the shared_buffers to 25% of system memory, so 12GB. (And since the new database is on 9.3, I didn't have to adjust the sysctl value for shmmax! Happy day!)
We used to have maintenance_work_mem set to something smaller, but we bumped that up after…<coughs>… the last time this database shut itself down to avoid wraparound in March 2012. We were hoping that would help speed the recovery at that time. Not sure if it did, but we left it that way afterward anyway.
On Sep 17, 2013, at 2:02 PM, bricklen <bricklen@gmail.com> wrote:
> On Tue, Sep 17, 2013 at 9:48 AM, Natalie Wenz <nataliewenz@ebureau.com> wrote:
> maintenance_work_mem | 10GB
> shared_buffers | 128MB
>
> maintenance_work_mem seems pretty high, and shared_buffers seems really low. Out of curiousity, were those set as a product of internal testing which determined those were effective settings?
>
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: nataliewenz@ebureau.com, bricklen@gmail.com
Subject: Re: Dumping a database that is not accepting commands?
In-Reply-To: <2EE7C659-6FA5-409D-8401-3F8A22E9DF3A@ebureau.com>
References: <B150080B-9E9A-456F-8B8D-110F07621165@ebureau.com> <1379421830.30619.YahooMailNeo@web162902.mail.bf1.yahoo.com> <A8C537BF-969B-41B9-8CFC-652F63E95F57@ebureau.com> <CAGrpgQ9TgYirUTDe6v1i_sat0j0aaAXy48nqP6cANKWAM5nqNg@mail.gmail.com> <2EE7C659-6FA5-409D-8401-3F8A22E9DF3A@ebureau.com>
* 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