On 01/29/2014 08:21 PM, Pavel Stehule wrote: > second question - is not this functionality too dangerous? If somebody > use it as scheduler, then > > a) can holds connect, session data, locks too long time > b) it can stop on query timeout probably much more early then user expect > > What is expected use case?
It is no more dangerous than plain pg_sleep(). The use case is convenience and clarity of code. I don't think people will be using it as a scheduler any more than they do with pg_sleep() because it can't cross transaction boundaries. -- Vik -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
