From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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 12:40:03 |
Message-ID: | 200309301240.h8UCe3r22317@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I assume it would be only setable by the super-user.
>
> 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?
> and only by a superuser.
See my recent email on this about "ownership". I personally am happy
with super-user only (or db-owner and super-user only). As I said, it
is a question of what documenting a foreign key in the system catalogs
means to folks who don't own the table.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | btober | 2003-09-30 12:57:47 | Re: Where are user-defined types stored/viewed |
Previous Message | Bruce Momjian | 2003-09-30 12:37:59 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-09-30 13:03:19 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
Previous Message | Bruce Momjian | 2003-09-30 12:37:59 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |