Kohei KaiGai <kai...@kaigai.gr.jp> writes:
> The reason why I redefined the relid of RangeTblEntry is to avoid
> the problem when security_barrier attribute get changed by concurrent
> transactions between rewriter and planenr stage.
This is complete nonsense. If the information is being injected into
the querytree by the rewriter, it's sufficient to assume that it's up to
date. Were it not so, we'd have problems with CREATE OR REPLACE RULE,
too.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
