From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, sthomas(at)peak6(dot)com, Maciek Sakrejda <msakrejda(at)truviso(dot)com>, felix <crucialfelix(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Really really slow select count(*) |
Date: | 2011-02-08 22:08:25 |
Message-ID: | 4D51BED9.3000407@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Scott Marlowe wrote:
> Are there any settings in postgresql.conf that would make it unsafe to
> use -m immediate?
>
Two concerns:
-Clients will be killed without any review, and data related to them lost
-The server will have to go through recovery to start back up again,
which could potentially take a long time. If you manage a successful
shutdown that doesn't happen.
Shouldn't be unsafe, just has those issues.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2011-02-08 22:14:46 | Re: Really really slow select count(*) |
Previous Message | Josh Berkus | 2011-02-08 22:04:59 | Re: Bad query plan when the wrong data type is used |