Re: pg_dumpall Sets Roll default_tablespace Before Creating Tablespaces

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dumpall Sets Roll default_tablespace Before Creating Tablespaces
Date: 2011-10-19 21:14:10
Message-ID: 70041807-3EE3-4A7C-BE13-6E7D98F42FBC@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 19, 2011, at 2:13 PM, Tom Lane wrote:

>> ALTER ROLE dude WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB LOGIN PASSWORD 'md5bdd7f8e73a214981b1519212b02a5530' VALID UNTIL 'infinity';
>> ALTER ROLE dude SET default_tablespace TO 'users';
>
> I'm beginning to think that the correct solution to these problems is to
> greatly restrict what you can set in ALTER ROLE/DATABASE SET. Or at
> least to document that if you use it, you get to keep both pieces after
> you break pg_dump.

Sorry, get to keep what two pieces?

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dan Ports 2011-10-19 21:20:11 Re: SSI implementation question
Previous Message Tom Lane 2011-10-19 21:13:13 Re: pg_dumpall Sets Roll default_tablespace Before Creating Tablespaces