| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: condition variables |
| Date: | 2016-10-23 17:00:23 |
| Message-ID: | CAM3SWZQFY8F5nga=xzoHE_4VfUpPkTYREpHMXtxmjN4=f56KEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 4, 2016 at 12:12 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> Here's a rebased patch. ConditionVariableSleep now takes
> wait_event_info. Anyone using this in patches for core probably needs
> to add enumerators to the WaitEventXXX enums in pgstat.h to describe
> their wait points.
I think that there are at least 2 patches from EDB people that are
already dependent on this one. I myself could easily adopt parallel
CREATE INDEX to use it, too. Why the continued delay in committing it?
I think it's fairly clear that this mechanism is widely useful.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2016-10-23 17:15:17 | Re: Exclude pg_largeobject form pg_dump |
| Previous Message | Petr Jelinek | 2016-10-23 15:26:18 | Re: PATCH: two slab-like memory allocators |