Re: PostgreSQL lock file

2019-08-12 Thread Олег Самойлов
> Best practice for this sort of thing is considered to be to run the two > Postgres instances under different user IDs. That avoids them thinking > that the other one's lock files are relevant, and it provides an extra > layer of security against possible conflicts between the two instances. >

Re: PostgreSQL lock file

2019-08-09 Thread Tom Lane
=?utf-8?B?0J7Qu9C10LMg0KHQsNC80L7QudC70L7Qsg==?= writes: > I have a task to create HA PostgreSQL cross datacenter cluster. I created a > test bed on VirtualBox and I simulate different failures and disastrous in > loops. And got one of funny bug of the Postgresql (11.4). One of the clusters > h

PostgreSQL lock file

2019-08-09 Thread Олег Самойлов
Hi all. I have a task to create HA PostgreSQL cross datacenter cluster. I created a test bed on VirtualBox and I simulate different failures and disastrous in loops. And got one of funny bug of the Postgresql (11.4). One of the clusters has two instances of PostgreSQL on port 5433 and 5434. Aft