From: | Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PQexec and timeouts |
Date: | 2002-12-12 02:09:28 |
Message-ID: | 3DF7EFD8.3020607@intransa.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ahaa....that is good....keep it comming....
Bruce Momjian wrote:
>Have you seen 'statement_timeout" SET parameter in 7.3?
>
>
>---------------------------------------------------------------------------
>
>Medi Montaseri wrote:
>
>
>>Is there any configuration parameter (run time or compile time) that would
>>allow me to timeout from a query.....
>>
>>ie, say I make a query (select or delete or whatever) against the
>>backend which
>>is using some disk off of a networked storage (NAS, SAN, etc)...
>>
>>I need to timeout if the resource (disk or the network) is wedged...
>>
>>If not, then what if I implement it using
>> PQsendQuery()
>> select on the connection socket with some timeout
>> if you haven't gotton your answer, abort the query...
>>
>>What is the best way to abort the query...I know of
>>
>>PQfinish() # too expensive, it closes the TCP connection
>>PQreset() # not sure but almost as expensive as PQfinish()
>>PQrequestCancel() # this sounds good...
>>
>>Thanks
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 3: if posting/reading through Usenet, please send an appropriate
>>subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>>message can get through to the mailing list cleanly
>>
>>
>>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2002-12-12 05:09:23 | Re: Potentially serious migration issue from 7.1.3 to 7.2 |
Previous Message | Fred Moyer | 2002-12-12 01:53:54 | Re: Urgent need of (paid) PostgreSQL support in New |