Re: pgsql: Update for roles: < * Prevent default re-use

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Update for roles: < * Prevent default re-use
Date: 2005-07-01 19:34:49
Message-ID: 20751.1120246489@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> The problem is this used in pg_dumpall --clean:

> DELETE FROM pg_shadow WHERE usesysid <> (SELECT datdba FROM pg_database WHERE datname = 'template0');

Hmm. I haven't gotten around to looking at pg_dumpall issues, but we
might have to add an ON DELETE rule to the pg_shadow view to allow old
dump files to continue working.

IIRC, there are *really* old dump files that try to do COPY TO
pg_shadow, but I'm assuming we don't care about supporting stuff
that far back.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-07-01 19:40:57 Re: pgsql: Update for roles: < * Allow limits on per-db/user connections >
Previous Message Tom Lane 2005-07-01 19:23:07 pgsql: Remove contrib version of rtree_gist --- now in core system.