Re: Re: Problem with disabling triggers in pg_dump
Peter Eisentraut <peter_e@gmx.net>
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Philip Warner <pjw@rhyme.com.au>, pgsql-hackers@postgresql.org, dyp@perchine.com
Date: 2000-07-25T20:40:25Z
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@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden