From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org, dyp(at)perchine(dot)com |
Subject: | Re: Re: Problem with disabling triggers in pg_dump |
Date: | 2000-07-25 20:40:25 |
Message-ID: | Pine.LNX.4.21.0007252048380.546-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane writes:
> We have talked about ways to solve the real problem. One way is to
> run the entire restore script as superuser, doing something other than
> \connect to set ownership of created objects. You could do that now
> with something like
> create table newtable ...
> update pg_class set relowner = xxx where relname = 'newtable';
> although it'd be nicer to invent ALTER commands to handle this.
And this is what good ol' SQL has in store for us:
CREATE SCHEMA AUTHORIZATION "username"
CREATE TABLE t1 (...)
CREATE TABLE t2 (...)
;
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-07-25 20:41:09 | Re: pg_dump, libdump, dump API, & backend again |
Previous Message | Peter Eisentraut | 2000-07-25 20:40:03 | Re: New Privilege model purposal |