1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix targetRelation initializiation in prepsecurity

Browse Source 
In 6f9bd50eabb0a4960e94c83dac8855771c9f340d, we modified
expand_security_quals() to tell expand_security_qual() about when the
current RTE was the targetRelation.  Unfortunately, that commit
initialized the targetRelation variable used outside of the loop over
the RTEs instead of at the start of it.

This patch moves the variable and the initialization of it into the
loop, where it should have been to begin with.

Pointed out by Dean Rasheed.

Back-patch to 9.4 as the original commit was.
This commit is contained in:
Stephen Frost 2015-03-01 15:26:55 -05:00
parent 8abb3cda0d
commit ee4ddcb38a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/optimizer/prep/prepsecurity.c
View File

@ -63,7 +63,6 @@ expand_security_quals(PlannerInfo *root, List *tlist)
Query *parse = root->parse;
int rt_index;
ListCell *cell;
bool targetRelation = false;
/*
* Process each RTE in the rtable list.
@ -74,7 +73,8 @@ expand_security_quals(PlannerInfo *root, List *tlist)
rt_index = 0;
foreach(cell, parse->rtable)
{
RangeTblEntry *rte = (RangeTblEntry *) lfirst(cell);
bool targetRelation = false;
RangeTblEntry *rte = (RangeTblEntry *) lfirst(cell);
rt_index++;