Hello all,
Can someone explain how *postgresql.auto.conf *file contents gets updated,
when running an alter system statement followed by pg_reload_conf?
I am trying to keep a symbolic link for the *postgresql.auto.conf* outside
the data directory. The link gets created but whenever I issue an alt
On 6/6/21 9:00 AM, RAJAMOHAN wrote:
Hello all,
Can someone explain how *postgresql.auto.conf *file contents gets
updated, when running an alter system statement followed by pg_reload_conf?
I am trying to keep a symbolic link for the
*postgresql.auto.conf* outside the data directory. The link
RAJAMOHAN writes:
> I am trying to keep a symbolic link for the *postgresql.auto.conf* outside
> the data directory. The link gets created but whenever I issue an alter
> system statement it gets broken.
This is not supported. Don't do it.
The right way to keep the hand-maintained config files
Yes, I learnt it the hard way as well :) I made changes via the alter
system, and did a pg_restore, and the changes were lost :)
use the alter system for ad hoc changes, but make sure those changes are
added back to the postgresql.conf file immediately (or however the main
conf file is managed).
On 6/6/21 10:02 AM, Vijaykumar Jain wrote:
Yes, I learnt it the hard way as well :) I made changes via the alter
system, and did a pg_restore, and the changes were lost :)
use the alter system for ad hoc changes, but make sure those changes are
added back to the postgresql.conf file immediate
On 6/6/21 10:50 AM, Vijaykumar Jain wrote:
Please reply to list also.
Ccing list
Also please use inline or bottom posting, it makes things easier to follow.
Yeah I am aware of that :)
I was referring to if the main config is managed via some config
management tool like puppet, ansible or an
this is a very interesting case. Atul keep us posted.
On 2021-06-03 22:51:55 +0200, Marc Millas wrote:
> postgres 12 with postgis.
> on a table we need a primary key and to get a unique combinaison, we need 3
> columns of that table:
> 1 of type integer,
> 1 of type text,
> 1 of type geometry
>
> creating the PK constraint doesn work:
I find that if
