Re: API change advice: Passing plan invalidation info from the rewriter into the planner?
От
Stephen Frost
Тема
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner?
Дата
Msg-id
20140415022324.GB2556@tamriel.snowman.net
Ответ на
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? (Tom Lane)
Список
Дерево обсуждения
API change advice: Passing plan invalidation info from the rewriter
into the planner? Craig Ringer <craig@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Craig Ringer <craig@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Craig Ringer <craig@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Adam Brightwell <adam.brightwell@crunchydatasolutions.com>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Craig Ringer <craig@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Craig Ringer <craig@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Kevin Grittner <kgrittn@ymail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Kevin Grittner <kgrittn@ymail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: RLS Design the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Dean Rasheed <dean.a.rasheed@gmail.com>
RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Dean Rasheed <dean.a.rasheed@gmail.com>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Dean Rasheed <dean.a.rasheed@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Dean Rasheed <dean.a.rasheed@gmail.com>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Dean Rasheed <dean.a.rasheed@gmail.com>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Kouhei Kaigai <kaigai@ak.jp.nec.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Kouhei Kaigai <kaigai@ak.jp.nec.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Kohei KaiGai <kaigai@kaigai.gr.jp>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Kohei KaiGai <kaigai@kaigai.gr.jp>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Robert Haas <robertmhaas@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Craig Ringer <craig@2ndquadrant.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: RLS Design Yeb Havinga <yebhavinga@gmail.com>
Re: RLS Design Dean Rasheed <dean.a.rasheed@gmail.com>
Re: RLS Design Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Dean Rasheed <dean.a.rasheed@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Alvaro Herrera <alvherre@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Craig Ringer <craig@2ndquadrant.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Gregory Smith <gregsmithpgsql@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? "Brightwell, Adam" <adam.brightwell@crunchydatasolutions.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Dean Rasheed <dean.a.rasheed@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Robert Haas <robertmhaas@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from the rewriter into the planner? Tom Lane <tgl@sss.pgh.pa.us>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Dean Rasheed <dean.a.rasheed@gmail.com>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? Stephen Frost <sfrost@snowman.net>
Re: API change advice: Passing plan invalidation info from
the rewriter into the planner? "Brightwell, Adam" <adam.brightwell@crunchydatasolutions.com>
Re: API change advice: Passing plan invalidation info from the
rewriter into the planner? Alvaro Herrera <alvherre@2ndquadrant.com>
* Tom Lane (tgl@sss.pgh.pa.us) wrote: > Stephen Frost writes: > > I've uploaded the latest patch, rebased against master, with my changes > > to here: http://snowman.net/~sfrost/rls_ringerc_sf.patch.gz as I don't > > believe it'd clear the mailing list (it's 29k). > > Please actually post it, for the archives' sake. 29k is far below the > list limit. (Which I don't know exactly what it is ... but certainly > in the hundreds of KB.) Huh, thought it was more like 25k. Well, here goes then... > > I'll take a look at changing the cache key to include user ID and > > ripping out the plan invalidation logic from the current patch tomorrow > > but I seriously doubt I'll be able to get all of that done in the next > > day or two. > > TBH I think we are up against the deadline. April 15 was the agreed-to > drop dead date for pushing new features into 9.4. Yeah. :/ May be for the best anyway, this should be able to go in early in the 9.5 cycle and get more testing and refinement. Still stinks though as I feel like this patch didn't get the attention it should have due to a simple misunderstanding, but we do need to stop at some point to get a release together. Thanks, Stephen
В списке pgsql-hackers по дате отправления