Re: Prevent conflicting SET options from being set

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prevent conflicting SET options from being set
Date: 2005-03-23 00:37:07
Message-ID: 200503230037.j2N0b7N11132@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Qingqing Zhou wrote:
>
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes
> >
> > We already have the ability to issue custom messages in assign_hooks,
> > and I think that's sufficient in practice.
>
> Yes, I agree this is already sufficient - seems we need to remove that TODO
> item in the list.

Removed. I think we have all the conflicting options fixed already:

< o Prevent conflicting SET options from being set
<
< This requires a checking function to be called after the server
< configuration file is read.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-03-23 01:30:14 Re: [HACKERS] what to do with backend flowchart
Previous Message Tom Lane 2005-03-23 00:07:23 Re: odd problem !