X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9314AD1B745 for ; Thu, 24 Jun 2004 14:29:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02623-01 for ; Thu, 24 Jun 2004 17:29:18 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 135F4D1B191 for ; Thu, 24 Jun 2004 14:29:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i5OHTDIC020710; Thu, 24 Jun 2004 13:29:13 -0400 (EDT) To: Alvaro Herrera Cc: Thomas Hallgren , pgsql-hackers@postgresql.org Subject: Re: bug in GUC In-reply-to: <20040624165542.GB2761@dcc.uchile.cl> References: <20040624052712.GA7158@dcc.uchile.cl> <13534.1088085728@sss.pgh.pa.us> <20040624165542.GB2761@dcc.uchile.cl> Comments: In-reply-to Alvaro Herrera message dated "Thu, 24 Jun 2004 12:55:42 -0400" Date: Thu, 24 Jun 2004 13:29:13 -0400 Message-ID: <20709.1088098153@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/872 X-Sequence-Number: 55422 Alvaro Herrera 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