From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rémi Zara <remi_zara(at)mac(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |
Date: | 2020-02-24 06:42:52 |
Message-ID: | CA+hUKGJ5+5qWtLGhq-HXJ1UUF2rOtmrCo1rtb+F_-UHTRmdmGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Mon, Feb 24, 2020 at 12:24 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> On reflection, trying to make ReserveExternalFD serve two different
> use-cases was pretty messy. Here's a version that splits it into two
> functions. I also took the trouble to fix dblink.
+ /*
+ * We don't want more than max_safe_fds / 3 FDs to be consumed for
+ * "external" FDs.
+ */
+ if (numExternalFDs < max_safe_fds / 3)
This looks pretty reasonable to me.
I'll have a new patch set to create a common WES at startup over on
that other thread in a day or two.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2020-02-24 06:53:34 | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |
Previous Message | Tom Lane | 2020-02-23 23:24:07 | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |
From | Date | Subject | |
---|---|---|---|
Next Message | Aditya Toshniwal | 2020-02-24 06:46:08 | PG v12.2 - Setting jit_above_cost is causing the server to crash |
Previous Message | Thomas Munro | 2020-02-24 03:55:35 | Re: Shouldn't GSSAPI and SSL code use FeBeWaitSet? |