Re: revamp row-security tracking - Mailing list pgsql-hackers

From Tom Lane
Subject Re: revamp row-security tracking
Date
Msg-id 933433.1739829296@sss.pgh.pa.us
Whole thread Raw
In response to Re: revamp row-security tracking  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes:
> Perhaps another variation
> on this idea is to create a query walker that just looks for hasRowSecurity
> flags throughout the tree (and to use that to mark the plan cache entry
> appropriately).

That seems like a pretty plausible compromise position.  So we'd
redefine Query.hasRowSecurity as summarizing the situation for only
the Query's own rtable entries, not recursively for sub-Queries.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Ayush Vatsa
Date:
Subject: Re: Clarification on Role Access Rights to Table Indexes
Next
From: Nathan Bossart
Date:
Subject: Re: describe special values in GUC descriptions more consistently