| 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 22:14:46 |
| Message-ID: | AANLkTi=BOpBe_23dqTqq7rKiP7H-0cGtVx-4+8n8LbJ5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Feb 8, 2011 at 3:08 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> 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.
Good, I was kinda worried about full_page_writes being off or fsync or
something like that being a problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Crooke | 2011-02-08 23:14:20 | Re: Bad query plan when the wrong data type is used |
| Previous Message | Greg Smith | 2011-02-08 22:08:25 | Re: Really really slow select count(*) |