postgres.git / summary / log / commit / refs

commit    195fbd40123b85ba8a44ca273b17d699e30ec6a8
Author:   Stephen Frost <sfrost@snowman.net>
Date:     Fri May 08 11:14:18 2015 +0000

    Remove reference to src/tools/backend/index.html
    
    src/tools/backend was removed back in 63f1ccd, but
    backend/storage/lmgr/README didn't get the memo.
    
    Author: Amit Langote


 src/backend/storage/lmgr/README | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/backend/storage/lmgr/README b/src/backend/storage/lmgr/README
index 6bc7efcdef2..8898e252272 100644
--- a/src/backend/storage/lmgr/README
+++ b/src/backend/storage/lmgr/README
@@ -56,9 +56,9 @@ two lock methods: DEFAULT and USER.
 Lock modes describe the type of the lock (read/write or shared/exclusive).
 In principle, each lock method can have its own set of lock modes with
 different conflict rules, but currently DEFAULT and USER methods use
-identical lock mode sets.  See src/tools/backend/index.html and
-src/include/storage/lock.h for more details.  (Lock modes are also called
-lock types in some places in the code and documentation.)
+identical lock mode sets. See src/include/storage/lock.h for more details.
+(Lock modes are also called lock types in some places in the code and
+documentation.)
 
 There are two main methods for recording locks in shared memory.  The primary
 mechanism uses two main structures: the per-lockable-object LOCK struct, and


[parent: 581f4f9657fc]