| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Greg Smith" <greg(at)2ndquadrant(dot)com>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "felix" <crucialfelix(at)gmail(dot)com>, "Marti Raudsepp" <marti(at)juffo(dot)org>,<sthomas(at)peak6(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, "Maciek Sakrejda" <msakrejda(at)truviso(dot)com> |
| Subject: | Re: Really really slow select count(*) |
| Date: | 2011-02-08 21:52:31 |
| Message-ID: | 4D5166BF020000250003A672@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
>> Kevin and I both suggested a "fast plus timeout then immediate"
>> behavior is what many users seem to want.
> Are there any settings in postgresql.conf that would make it
> unsafe to use -m immediate?
I don't think so. There could definitely be problems if someone
cuts power before your shutdown completes, though. (I hear that
those firefighters like to cut power to a building before they grab
those big brass nozzles to spray a stream of water into a building.
Go figure...)
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-02-08 22:04:59 | Re: Bad query plan when the wrong data type is used |
| Previous Message | Scott Marlowe | 2011-02-08 21:41:00 | Re: Really really slow select count(*) |