| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Marti Raudsepp <marti(at)juffo(dot)org> |
| Cc: | 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 20:09:40 |
| Message-ID: | 4D51A304.4070003@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Marti Raudsepp wrote:
> I couldn't find any past discussions about changing the default to "fast".
> Are there any reasons why that cannot be done in a future release?
>
Well, it won't actually help as much as you might think. It's possible
for clients to be in a state where fast shutdown doesn't work, either.
You either have to kill them manually or use an immediate shutdown.
Kevin and I both suggested a "fast plus timeout then immediate" behavior
is what many users seem to want. My comments were at
http://archives.postgresql.org/pgsql-hackers/2009-09/msg01145.php ; for
an example of how fast shutdown can fail see
http://archives.postgresql.org/pgsql-bugs/2009-03/msg00062.php
--
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 | Marti Raudsepp | 2011-02-08 21:09:46 | Re: Really really slow select count(*) |
| Previous Message | Sylvain Rabot | 2011-02-08 20:08:54 | Re: Indexes with condition using immutable functions applied to column not used |