From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
---|---|
To: | "Francois Rigaudie" <francois(dot)rigaudie(at)tdf(dot)fr> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: dblink locked query |
Date: | 2006-11-23 10:19:32 |
Message-ID: | 52EF20B2E3209443BC37736D00C3C1380B8EF484@EXADV1.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane answered to a question from Francois Rigaudie:
>> Since there is no timeout possibility with dblink I look for a
solution to
>> that problem.
>
> Doesn't statement_timeout work?
To expand on this:
dblink will login as a certain user on the remote database.
If your design is good, this is a dedicated user only for this
purpose.
You can then
ALTER ROLE <user> SET statement_timeout = 10000
for that user on the remote database to have all statements
canceled when they take longer than 10 seconds.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Francois Rigaudie | 2006-11-23 10:44:26 | Rép. : Re: dblink locked query |
Previous Message | Peter Eisentraut | 2006-11-23 09:23:37 | Vacuum columns in statistics tables |