Re: WIP fix proposal for bug #6123

From: "Kevin Grittner" <kgrittn(at)mail(dot)com>
To: "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP fix proposal for bug #6123
Date: 2012-10-25 13:53:16
Message-ID: 20121025135316.306930@gmx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Kevin Grittner escribió:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

Sorry I just got to this in wading through backlog. Will push today
without docs and work on docs soon.

-Kevin

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2012-10-25 13:57:38 Re: autovacuum truncate exclusive lock round two
Previous Message Tom Lane 2012-10-25 13:52:10 Re: unfixed bugs with extensions