CreateFakeRelcacheEntry versus Hot Standby - Mailing list pgsql-hackers

From Tom Lane
Subject CreateFakeRelcacheEntry versus Hot Standby
Date
Msg-id 27207.1265740630@sss.pgh.pa.us
Whole thread Raw
Responses Re: CreateFakeRelcacheEntry versus Hot Standby
List pgsql-hackers
I was rather surprised to find this code still present:
/* * We set up the lockRelId in case anything tries to lock the dummy * relation.  Note that this is fairly bogus since
relNodemay be * different from the relation's OID.  It shouldn't really matter though, * since we are presumably
runningby ourselves and can't have any lock * conflicts ... */rel->rd_lockInfo.lockRelId.dbId =
rnode.dbNode;rel->rd_lockInfo.lockRelId.relId= rnode.relNode;
 

Seems quite unsafe in HS.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: bugfix - VIP: variadic function ignore strict flag
Next
From: Tom Lane
Date:
Subject: Why doesn't smgr_redo truncate the VM fork too?