Takahiro Itagaki wrote:
Fujii Masao masao.fu...@gmail.com wrote:
The attached patch changes the lock mode which pg_start_backup()
uses. Is it worth applying this patch?
I think the patch is reasonable to represent what we are doing,
even if there is no performance benefits from it.
Agreed.
Fujii Masao masao.fu...@gmail.com wrote:
Currently pg_start_backup() accesses the shared ControlFile
by using ControlFileLock with LW_EXCLUSIVE lock mode. But
since that access is read-only operation, LW_SHARED should
be chosen instead of LW_EXCLUSIVE.
The attached patch changes the lock
Hi,
Currently pg_start_backup() accesses the shared ControlFile
by using ControlFileLock with LW_EXCLUSIVE lock mode. But
since that access is read-only operation, LW_SHARED should
be chosen instead of LW_EXCLUSIVE.
The attached patch changes the lock mode which pg_start_backup()
uses. Is it
Fujii Masao masao.fu...@gmail.com wrote:
Currently pg_start_backup() accesses the shared ControlFile
by using ControlFileLock with LW_EXCLUSIVE lock mode. But
since that access is read-only operation, LW_SHARED should
be chosen instead of LW_EXCLUSIVE.
Almost all operations of
