Re: pgsql: Add kqueue(2) support to the WaitEventSet API.
От | Thomas Munro |
---|---|
Тема | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |
Дата | |
Msg-id | CA+hUKGJeL9XP8p5c4fGoAgPU9ktuxpiCt6An4N9ytO=qSh9WgA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: pgsql: Add kqueue(2) support to the WaitEventSet API.
|
Список | pgsql-hackers |
On Mon, Feb 24, 2020 at 7:42 PM Thomas Munro <thomas.munro@gmail.com> wrote: > On Mon, Feb 24, 2020 at 12:24 PM Tom Lane <tgl@sss.pgh.pa.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) I suppose there may be users who have set ulimit -n high enough to support an FDW workload that connects to very many hosts, who will now need to set max_files_per_process higher to avoid the new error now that we're doing this accounting. That doesn't seem to be a problem in itself, but I wonder if the error message should make it clearer that it's our limit they hit here.
В списке pgsql-hackers по дате отправления: