Re: [v9.2] Fix Leaky View Problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [v9.2] Fix Leaky View Problem
Date
Msg-id 205.1317067179@sss.pgh.pa.us
Whole thread Raw
In response to [v9.2] Fix Leaky View Problem  (Kohei Kaigai <Kohei.Kaigai@EMEA.NEC.COM>)
Responses Re: [v9.2] Fix Leaky View Problem
Re: [v9.2] Fix Leaky View Problem
List pgsql-hackers
Kohei KaiGai <kaigai@kaigai.gr.jp> writes:
> Sorry, are you saying the current (in other words, rte->security_barrier
> stores the state of reloption) approach is not a good idea?

Yes.  I think the same as Robert: the way to handle this is to store it
in RelOptInfo for the duration of planning, and pull it from the
catalogs during planner startup (cf plancat.c).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: contrib/sepgsql regression tests are a no-go
Next
From: Kohei KaiGai
Date:
Subject: Re: [v9.2] Fix Leaky View Problem