From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, Darren King <darrenk(at)insightdist(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Postgres acl (fwd) |
Date: | 1998-01-07 02:18:01 |
Message-ID: | Pine.NEB.3.96.980106221220.254k-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 7 Jan 1998, Thomas G. Lockhart wrote:
> Are there any maintenance operations which require a "delete from pg_xxx"? If
> not, then we could just modify the parser (or the executor?) to check the table
> name and not allow insert/delete from any table whose name starts with "pg_". Had
> to ask, although I'm sure this is too easy to actually work :)
As long as what you are suggesting doesn't break "drop database", "drop
table", "drop view"...I realize that this is obvious, but...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-01-07 02:19:15 | Re: [HACKERS] PostODBC... |
Previous Message | Bruce Momjian | 1998-01-07 02:16:20 | Re: [HACKERS] VACUUM error on CVS build 07-JAN-98 |