public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Thomas Hallgren <[email protected]>
Cc: [email protected]
Subject: Re: bug in GUC
Date: Thu, 24 Jun 2004 13:29:13 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Alvaro Herrera <[email protected]> writes:
> I'm not sure exactly why this is a good idea.  After all, if the systems
> runs out of memory while starting up, what can be expected later?

The issue isn't with startup, but with re-reading postgresql.conf due to
SIGHUP later on.  We don't want to elog(ERROR) partway through that
process.  Especially not in the postmaster, where elog(ERROR) is
tantamount to elog(FATAL).  (But of course the postmaster shouldn't ever
run out of memory anyway...)

It's possible that this should all be rethought, but it would be a much
more wide-ranging change than we've been discussing.

			regards, tom lane

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: bug in GUC
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox