| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexandr Blinov <alexandr(dot)blinov(at)mysky(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Alexander Saltanov <asd(at)mysky(dot)com> |
| Subject: | Re: BUG: postgresql.auto.conf location |
| Date: | 2018-05-30 18:14:24 |
| Message-ID: | 2426.1527704064@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alexandr Blinov <alexandr(dot)blinov(at)mysky(dot)com> writes:
> After that the following command is executed: ALTER SYSTEM SET max_connections = xxx;'
> File postgresql.auto.conf is be created at 'data' directory, although this is expected in the same directory as the main postgresql.conf file.
That's intentional, and indeed necessary. If you are keeping the main
config file in some other place, it's likely that that other place isn't
even writable by the server.
> This is a confusing, because in case of backup/restore or pg_basebackup to a new server (or new slave server), auto.conf file also will be transferred and applied to a new server, which in some cases is not expected.
There's been some discussion of teaching those tools to not copy config
files (perhaps optionally?), but I'm not sure what the current status is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 158306855 | 2018-05-31 03:58:53 | Re: [BUG] postgresql replaying WAL slowly when master drop a largenumber of relations in one transaction |
| Previous Message | David G. Johnston | 2018-05-30 17:43:53 | Re: BUG: postgresql.auto.conf location |