Re: Analyzing bug 8049 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Analyzing bug 8049
Date
Msg-id CA+TgmoYasRrz42dSku12WxuoNM6Dydi42Bev4ZwWoCYDma738g@mail.gmail.com
Whole thread Raw
In response to Analyzing bug 8049  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Analyzing bug 8049
List pgsql-hackers
On Thu, Apr 11, 2013 at 1:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This idea needs more fleshing out, but it's seeming awfully attractive
> right now.  The big problem with it is that it's going to be a more
> invasive patch than I feel terribly comfortable about back-patching.
> However, I'm not sure there's much choice, because I don't see any narrow
> fix for 9.2 that would not result in very substantial degradation of its
> optimization ability.  We can't just lobotomize equivalence-class
> processing.
>
> The plan I'm considering is to get this written and committed to HEAD
> in the next week, so that it can go out in 9.3beta1.  After the patch
> has survived a reasonable amount of beta testing, I'd be more comfortable
> about back-patching into 9.2.

I'm not very sanguine about the chances that back-patching this won't
provoke any screams of agony ... but I don't have a better idea,
either.  Letting queries return wrong answers isn't a superior
solution, for sure.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [sepgsql 2/3] Add db_schema:search permission checks
Next
From: Robert Haas
Date:
Subject: Re: [sepgsql 2/3] Add db_schema:search permission checks