14.02.2013 10:03, Takatoshi MATSUO пишет:
> Hi
>
> 2013/2/13 Andrew :
>> 12.02.2013 02:35, Takatoshi MATSUO пишет:
>>
>>> Hi
>>>
>>> 2013/2/9 Andrew :
Hi all.
For what reason is implemented PGSQL.lock in RA, and what pbs may happen
if
it'll be removed from RA code?
>>> It may ca
Hi
2013/2/13 Andrew :
> 12.02.2013 02:35, Takatoshi MATSUO пишет:
>
>> Hi
>>
>> 2013/2/9 Andrew :
>>>
>>> Hi all.
>>> For what reason is implemented PGSQL.lock in RA, and what pbs may happen
>>> if
>>> it'll be removed from RA code?
>>
>> It may cause data inconsistency.
>> If the file exists in a
12.02.2013 02:35, Takatoshi MATSUO пишет:
Hi
2013/2/9 Andrew :
Hi all.
For what reason is implemented PGSQL.lock in RA, and what pbs may happen if
it'll be removed from RA code?
It may cause data inconsistency.
If the file exists in a node, you need to copy data from new master.
I noticed that
Hi
2013/2/9 Andrew :
> Hi all.
> For what reason is implemented PGSQL.lock in RA, and what pbs may happen if
> it'll be removed from RA code?
It may cause data inconsistency.
If the file exists in a node, you need to copy data from new master.
> Also, 2nd question: how I can prevent pgsql RA fro
Hi all.
For what reason is implemented PGSQL.lock in RA, and what pbs may happen
if it'll be removed from RA code?
Also, 2nd question: how I can prevent pgsql RA from promoting master
before both nodes will brings up OR before timeout is reached (for ex.,
if 2nd node is dead)? I think that cl
