| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Julie Nishimura <juliezain(at)hotmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: default_tablespace in 8.3 postgresql |
| Date: | 2019-05-15 22:22:53 |
| Message-ID: | 7ad4ffc6-ffd9-7539-71e8-99b9e3d96d4f@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julie Nishimura | 2019-05-15 22:23:52 | Re: default_tablespace in 8.3 postgresql |
| Previous Message | Julie Nishimura | 2019-05-15 22:20:42 | Re: default_tablespace in 8.3 postgresql |