Re: WIP fix proposal for bug #6123 - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: WIP fix proposal for bug #6123
Date
Msg-id 20121026200605.306890@gmx.com
Whole thread Raw
In response to WIP fix proposal for bug #6123  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Alvaro Herrera wrote:
> Kevin Grittner escribió:
>> Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
>>> Also, it doesn't appear that we ever got around to preparing
>>> documentation updates, but I think we definitely need some if
>>> we're going to start throwing errors for things that used to be
>>> allowed. Since Kevin has the most field experience with this
>>> problem, I'd like to nominate him to write some docs ...
>> 
>> OK, will do. The "redo the DELETE and RETURN NULL" workaround is
>> not at all obvious; we should definitely include an example of
>> that.
> 
> Any chance this patch could be pushed soon?
> 
> The problem is that this patch conflicts rather heavily with my FOR
> KEY SHARE patch. I think it makes sense to commit this one first.
> 
> To me, it would be good enough that the code changes go in now; the
> doc patch can wait a little longer.

OK, pushed after reviewing the the archive threads, rebasing the
patch, and testing.

Doc patch to follow.

-Kevin



pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: Re: Query ending up with hitting all the partition with sub-query in the projection list
Next
From: Josh Berkus
Date:
Subject: Re: [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility