On 09/06/17 20:56, Andres Freund wrote:
> On 2017-06-08 23:04:31 -0700, Noah Misch wrote:
>> On Wed, Jun 07, 2017 at 10:54:57PM -0700, Noah Misch wrote:
>>> On Fri, Jun 02, 2017 at 11:06:29PM -0700, Andres Freund wrote:
>>>> On 2017-06-02 22:12:46 -0700, Noah Misch wrote:
>>>>> On Fri, Jun 02, 2017 at 11:27:55PM -0400, Peter Eisentraut wrote:
>>>>>> On 5/31/17 23:54, Peter Eisentraut wrote:
>>>>>>> On 5/29/17 22:01, Noah Misch wrote:
>>>>>>>> On Tue, May 23, 2017 at 01:45:59PM -0400, Andres Freund wrote:
>>>>>>>>> On May 23, 2017 1:42:41 PM EDT, Petr Jelinek <petr.jelinek@2ndquadrant.com> wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> so this didn't really move anywhere AFAICS, do we think the approach
>>>>>>>>>> I've chosen is good or do we want to do something else here?
>>>>>>>>>
>>>>>>>>> Can you add it to the open items list?
>>>>>>>>
>>>>>>>> [Action required within three days. This is a generic notification.]
>>>>>>>
>>>>>>> I have posted an update. The next update will be Friday.
>>>>>>
>>>>>> Andres is now working on this. Let's give him a bit of time. ;-)
>>>>>
>>>>> If you intended this as your soon-due status update, it is missing a mandatory
>>>>> bit.
>>>>
>>>> I'm now owning this item. I've posted patches, await review. If none
>>>> were to be forthcoming, I'll do another pass Monday, and commit.
>>>
>>> This PostgreSQL 10 open item is past due for your status update. Kindly send
>>> a status update within 24 hours, and include a date for your subsequent status
>>> update. Refer to the policy on open item ownership:
>>> https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com
>>
>> IMMEDIATE ATTENTION REQUIRED. This PostgreSQL 10 open item is long past due
>> for your status update. Please reacquaint yourself with the policy on open
>> item ownership[1] and then reply immediately. If I do not hear from you by
>> 2017-06-10 07:00 UTC, I will transfer this item to release management team
>> ownership without further notice.
>
> The issue starting this thread is resolved, including several issues
> found in its wake, with 47fd420fb4d3e77dde960312f8672c82b14ecbad
> 6e1dd2773eb60a6ab87b27b8d9391b756e904ac3 and c1abe6c786d8f00643de8519140d77644b474163
>
> There's a remaining testing patch, and some related things left though.
> Basically patches 0001 and 0003 from
> http://archives.postgresql.org/message-id/81eaca60-3f7b-6a21-5531-fd51ffbf3f63%402ndquadrant.com
> I'd personally rather see a separate open-items entry for those, since
> this isn't related to paralellism, signal handler or such.
>
> Petr, Peter (henceforth P^2), do you agree?
Makes sense, one could argue that 0003 could be even 2 open items with 2
patches - one with the fixes for parser and one for the other type of
message support (I am not even sure if we want to add other message
support into PG10).
-- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services