Skip site navigation (1) Skip section navigation (2)

Re: max_files_per_process ignored on Windows

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: max_files_per_process ignored on Windows
Date: 2012-03-28 16:19:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Mar 28, 2012 at 18:12, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> At postmaster startup, we determine the maximum number of open files we can
> handle by trying to open a lot of file descriptors, up to
> max_files_per_process. This is done in set_max_safe_fds(), and the
> determined max_safe_fds value is inherited by child processes at fork().
> However, with EXEC_BACKEND, ie. Windows, it's not inherited, so we always
> run with the initial conservative default of 32.
> 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.

> Thoughts? Although this has apparently always been like this, no-one has
> complained, so I'm thinking that we shouldn't backport this.

We should absolutely *not* backport this. It needs to go through some
proper testing first, it might cause serious effects on some systems.
In particular, it might have yet another round of effects on people
who run with AV enabled...

 Magnus Hagander

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2012-03-28 16:29:27
Subject: Re: Finer Extension dependencies
Previous:From: Jaime CasanovaDate: 2012-03-28 16:13:34
Subject: Re: Review of pg_archivecleanup -x option patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group