pgsql: pg_start_backup() can use a share lock to lock ControlFileLock

From: itagaki(at)postgresql(dot)org (Takahiro Itagaki)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: pg_start_backup() can use a share lock to lock ControlFileLock
Date: 2010-03-10 02:04:49
Message-ID: 20100310020449.432577541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
pg_start_backup() can use a share lock to lock ControlFileLock
instead of an exclusive lock.

The change is almost for code cleanup. Since there seems to be no
performance benefits from it, backports should not be needed.

Fujii Masao

Modified Files:
--------------
pgsql/src/backend/access/transam:
xlog.c (r1.379 -> r1.380)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.379&r2=1.380)

Browse pgsql-committers by date

  From Date Subject
Next Message User Itagaki 2010-03-10 08:10:02 pgstatsinfo - pg_statsinfo: Support PostgreSQL 8.3 and various fixes.
Previous Message Tom Lane 2010-03-10 01:59:31 pgsql: Preliminary release notes for releases 8.4.3, 8.3.10, 8.2.16,