Re: Re: Problem with disabling triggers in pg_dump - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Re: Problem with disabling triggers in pg_dump
Date
Msg-id Pine.LNX.4.21.0007252048380.546-100000@localhost.localdomain
Whole thread Raw
In response to Re: Problem with disabling triggers in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: New Privilege model purposal
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_dump, libdump, dump API, & backend again