I agree with Adrian. If this is on a Linux system, I'd suggest setting up
"icrond" to monitor that file and at least record who is accessing it. In
addition, I would suggest that said Linux system run with SELinux in
"enforcing" mode. That can stop even "root" from updating something, if it
More importantly, what version of PostgreSQL and what O/S are you working
with.
If this is Ubuntu, you could simply be looking at the wrong postgresql.conf
file.
On Tue, Nov 17, 2015 at 7:33 AM, John McKown
wrote:
> I agree with Adrian. If this is on a Linux
On 11/16/2015 06:59 PM, M Tarkeshwar Rao wrote:
Hi All,
In our production setup we found new issue as postgreSQL.conf has become
zero byte file.
After some time we copied that file from some back up, after some time
it has again become zero byte.
Any clue what is the reason of this behavior.
Hi All,
In our production setup we found new issue as postgreSQL.conf has become zero
byte file.
After some time we copied that file from some back up, after some time it has
again become zero byte.
Any clue what is the reason of this behavior.
Regards
Tarkeshwar