Nope, I did not...
pg_roles only shows "rolconfig" as {default_transaction_read_only=true} for some users...
The only other commands I ran between creation of tablespace and alter dbs are:
grant all on tablespace vol4 to public;
grant create on tablespace vol4 to public;
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: Wednesday, May 15, 2019 3:22 PM
To: Julie Nishimura; David G. Johnston
Cc: pgsql-general@lists.postgresql.org
Subject: Re: default_tablespace in 8.3 postgresql
On 5/15/19 3:01 PM, Julie Nishimura wrote:
> No, I did not have them at all in my script. I did not touch neither
> these three dbs, nor like some others that I did not intend to alter,
> but they are altered regardless. Or unless this is what pg_database
> reports back to me... What is even more interesting, if I use PGAdmin
> for one of the dbs that I was not intended to alter and leave it on
> vol3, this is what it shows to me now. Please note, it shows both -
> "Default tablespace" (as vol3), and "default_tablespace" (as vol4)... Hmm...
>
You didn't happen to do a:
ALTER ROLE some_role SET default_tablespace = 'vol4';
Do:
select rolname, rolconfig from pg_roles;
--
Adrian Klaver
adrian.klaver@aklaver.com