Re: max_files_per_process ignored on Windows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: max_files_per_process ignored on Windows
Date: 2012-03-29 02:02:45
Message-ID: 9225.1332986565@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Wed, Mar 28, 2012 at 18:12, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> An obvious fix would be to call set_max_safe_fds() in the child processes,
>> although I wonder if that's too expensive. Another option is to pass down
>> the value with save_restore_backend_variables().

> ISTM that passing down through save_restore_backend_variables() is a
> much better choice.

+1. Having multiple children running set_max_safe_fds() concurrently
would be a seriously bad idea.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-03-29 02:12:05 Re: pgxs and bison, flex
Previous Message Joachim Wieland 2012-03-29 01:54:53 Re: patch for parallel pg_dump