Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)

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: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Childs <Blue(dot)Dragon(at)blueyonder(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
Date: 2003-09-30 13:58:01
Message-ID: 19068.1064930281@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:
> Tom Lane wrote:
>> That might be a good restriction too (on top of my speculation about not
>> allowing it in postgresql.conf). Only allow it to be SET per-session,

> We don't have a way to make something unsetable in postgresql.conf right
> now, do we?

Yeah, we do --- see GUC_DISALLOW_IN_FILE. The existing variable
zero_damaged_pages has the same restrictions we're talking about here,
and for largely the same reasons: you can shoot yourself in the foot
with it.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Creager 2003-09-30 14:06:25 Re: Divide by zero...
Previous Message Mike Mascari 2003-09-30 13:54:43 Re: Functional index performance question

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-09-30 14:07:51 Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
Previous Message Tom Lane 2003-09-30 13:49:40 Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)