From: | pinker <pinker(at)onet(dot)eu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | pg_sleep() inside plpgsql block - pro & cons |
Date: | 2018-10-02 10:10:03 |
Message-ID: | 1538475003972-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi!
There is second time I see that somebody uses pg_sleep function inside
plpgsql block. This case is quite similar to the last one - it's some kind
of wait for data to be loaded. After pg_sleep there is a check if some
condition is true, if not procedure goes to sleep again. As a result an
average duration of this function is 1,5h...
I'm trying to gather pros and cons regarding using pg_sleep this way. What's
coming to my mind are only 2 cons:
* clog contention
* long running open transactions (which is quite good described in here:
https://www.simononsoftware.com/are-long-running-transactions-bad/)
So maybe you'll add some more to the list?
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Olarte | 2018-10-02 10:26:25 | Re: pg_sleep() inside plpgsql block - pro & cons |
Previous Message | Dean Rasheed | 2018-10-02 08:28:15 | Re: Postgres trigger side-effect is occurring out of order with row-level security select policy |