Re: postmaster -d option (was Re: [GENERAL] Relation 0 does not exist)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: postmaster -d option (was Re: [GENERAL] Relation 0 does not exist)
Date: 2002-09-26 14:11:09
Message-ID: 3713.1033049469@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> diff -c -c -r1.294 postgres.c
> *** src/backend/tcop/postgres.c 25 Sep 2002 20:31:40 -0000 1.294
> --- src/backend/tcop/postgres.c 26 Sep 2002 05:15:41 -0000
> ***************
> *** 1281,1288 ****
> * -d 0 allows user to prevent postmaster debug
> * from propagating to backend.
> */
> ! SetConfigOption("server_min_messages", "notice",
> ! ctx, gucsource);
> }
> break;

> --- 1281,1287 ----
> * -d 0 allows user to prevent postmaster debug
> * from propagating to backend.
> */
> ! ResetPGVariable("server_min_messages");
> }
> break;

If you want "export PGOPTIONS=-d0" to do what the comment says, you'd
also need to Reset all of the other GUC variables that -dN might have
set. However, I'm not sure that I agree with the goal in the first
place. If the admin has set debugging on the postmaster command line,
should it really be possible for users to turn it off so easily?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Manfred Koizar 2002-09-26 14:14:10 Re: Nicer dump files?
Previous Message Tom Lane 2002-09-26 13:59:32 Re: Relation 0 does not exist

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB SD 2002-09-26 14:19:15 Re: AIX compilation problems (was Re: Proposal ...)
Previous Message Tom Lane 2002-09-26 14:05:11 Re: Insert Performance