Re: lock mode for ControlFileLock which pg_start_backup uses - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: lock mode for ControlFileLock which pg_start_backup uses
Date
Msg-id 20100309164721.99CA.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to lock mode for ControlFileLock which pg_start_backup uses  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: lock mode for ControlFileLock which pg_start_backup uses
List pgsql-hackers
Fujii Masao <masao.fujii@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 ControlFileLock is in LW_EXCLUSIVE, but
there is one usage of LWLockConditionalAcquire(ControlFileLock, LW_SHARED)
in XLogNeedsFlush().

> 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.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: invalid UTF-8 via pl/perl
Next
From: Takahiro Itagaki
Date:
Subject: Re: Visual Studio 2005, C-language function - avoiding hacks?