Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on
Date: 2009-07-25 17:50:19
Message-ID: 12943.1248544219@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

mha(at)postgresql(dot)org (Magnus Hagander) writes:
> Log Message:
> -----------
> Reserve the shared memory region during backend startup on Windows, so
> that memory allocated by starting third party DLLs doesn't end up
> conflicting with it.

I am wondering why failure of the various TerminateProcess calls in
postmaster.c is elog(ERROR) and not elog(LOG). While that probably
shouldn't happen, aborting the postmaster isn't a good response if it
does. This patch introduces a new occurrence, but I see it is just
copying what was there already.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-07-26 23:34:18 pgsql: Extend EXPLAIN to allow generic options to be specified.
Previous Message Andrew Dunstan 2009-07-25 17:21:04 Re: pgsql: Small stylistic improvement in recent FORCE QUOTE * code - use a

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-07-25 17:55:21 Re: proposal: support empty string as separator for string_to_array
Previous Message Tom Lane 2009-07-25 17:35:29 Re: proposal: support empty string as separator for string_to_array