| From: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
|---|---|
| To: | Ragnar <gnari(at)hive(dot)is> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: query timeout |
| Date: | 2006-03-03 10:03:33 |
| Message-ID: | 7EFA54E3-FF6B-4E3D-9C0C-8191A7748B04@alpinenetworking.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Oh that will abort vacuum after that time as well? Can anyone
confirm that this is the case? There shouldn't be ANY queries that
take that long and if there are then can manually set the parameter
when those requests happen. I would prefer to limit by default and
allow longer queries only when I specify. But if it kills vacuum I
will have to take a different approach.
On Mar 3, 2006, at 2:59 AM, Ragnar wrote:
> On fim, 2006-03-02 at 11:03 -0700, Rick Gigger wrote:
>> Never-mind that. I'm assuming statement_timeout is what I need?
>
> Yes, but take care if you change this in postgresql.conf:
> some queries might reasonaby be expected to take longer
> than 5 minutes, such as VACUUM.
>
> gnari
>
>> On Mar 2, 2006, at 11:01 AM, Rick Gigger wrote:
>>
>>> Is there a way to put a timeout on a query so that if it runs
>>> longer than 5 minutes or something it is just automatically
>>> terminated?
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2006-03-03 10:14:20 | Re: query timeout |
| Previous Message | Paul Mackay | 2006-03-03 10:03:24 | Physical column size |