Postgres Pro
Downloads
Home   >   mailing lists

Why do we keep UnusedLock1 in LWLockId? - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Why do we keep UnusedLock1 in LWLockId?
Date
Msg-id 20090303154657.8F29.52131E4D@oss.ntt.co.jp
Whole thread Raw
Responses Re: Why do we keep UnusedLock1 in LWLockId?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Tree view 
Hi,

There is UnusedLock1 in LWLockId enumerations in storage/lwlock.h .
|    UnusedLock1,                /* FreeSpaceMapLock used to be here */

I thought it is for keeping LWLockId same as 8.3 at first,
but we've already split SInvalLock to SInvalReadLock and
SInvalWriteLock. So the IDs are changed anyway.

Are there any reason to keep UnusedLock1 there?
Or can we remove it simpley?

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

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: SIGHUP during recovery
Next
From: KaiGai Kohei
Date:
Subject: Updates of SE-PostgreSQL 8.4devel patches (r1668)