| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(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 21:41:00 |
| Message-ID: | AANLkTikFaJsaR_4M8rw4Wwyu_N+5yx2+7MQOZgXPt-kX@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Feb 8, 2011 at 1:09 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> 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?
>>
> 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
Are there any settings in postgresql.conf that would make it unsafe to
use -m immediate?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-02-08 21:52:31 | Re: Really really slow select count(*) |
| Previous Message | Kevin Grittner | 2011-02-08 21:20:23 | Re: Really really slow select count(*) |