| From: | Thomas Munro <tmunro(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Allow condition variables to be used in interrupt code. |
| Date: | 2021-03-01 04:45:35 |
| Message-ID: | E1lGaR5-0000lC-K0@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Allow condition variables to be used in interrupt code.
Adjust the condition variable sleep loop to work correctly when code
reached by its internal CHECK_FOR_INTERRUPTS() call interacts with
another condition variable.
There are no such cases currently, but a proposed patch would do this.
Discussion: https://postgr.es/m/CA+hUKGLdemy2gBm80kz20GTe6hNVwoErE8KwcJk6-U56oStjtg@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/f5a5773a9dc4185414fe538525e20d8512c2ba35
Modified Files
--------------
src/backend/storage/lmgr/condition_variable.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-03-01 15:25:21 | Re: pgsql: Add TID Range Scans to support efficient scanning ranges of TIDs |
| Previous Message | Amit Kapila | 2021-03-01 03:51:47 | pgsql: Avoid repeated decoding of prepared transactions after a restart |