| 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-16 00:38:52 |
| Message-ID: | 88c6a5fa-7ca9-9870-fd35-6477be0954e9@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/15/19 5:29 PM, Julie Nishimura wrote:
> Guys, thank you everybody who tried to solve this mystery! It is solved
> now. I went through the logs and found those "alter database" commands,
> based on host and time, I've just found shell script which was executing
> from crontab and setting all databases (except system ones and control)
> default_tablespace to the emptiest volume...
Aah, that explains it. Good to find the cause.
>
> Thanks everybody...
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2019-05-16 07:12:19 | Re: terminating walsender process due to replication timeout |
| Previous Message | Julie Nishimura | 2019-05-16 00:29:48 | Re: default_tablespace in 8.3 postgresql |