Re: So where are we on the open commitfest? - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: So where are we on the open commitfest?
Date
Msg-id CAHGQGwE6isC+K_AUDRbYT=kGk8RexvmujryNrafHc-Ps_1RMHQ@mail.gmail.com
Whole thread Raw
In response to Re: So where are we on the open commitfest?  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: So where are we on the open commitfest?  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Sat, Oct 29, 2011 at 5:50 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Fri, Oct 28, 2011 at 8:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>> * Separating bgwriter and checkpointer
>>
>> Same for this one.
>
> Will commit by end of Monday

There are plenty of source comments (and probably documents) describing that
checkpoint is performed by bgwriter, but the patch that you posted
didn't correct
them. Are you going to include the change of them in the patch? Or commit
separately?

>> * pg_last_xact_insert_timestamp
>>
>> This one is stuck because we don't have consensus on whether it should
>> be applied.  I suggest pushing it forward to the next 'fest to give
>> Simon a reasonable amount of time to come up with a counterproposal.
>> (At some point, though, we should commit it if he doesn't provide one.)
>
> +1

+1

>> * unite recovery.conf and postgresql.conf
>>
>> This one also seems to be lacking consensus more than anything else.
>> What do we do about that?
>
> I'll re-read the thread in detail to see if I can break impasse.

That's very helpful. I'd like to hear what you think we should not change
for the backward compatibility, and what we can do. AFAIR you agreed
to rename recovery.conf, so I don't guess that you want 100% compatibility.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: So where are we on the open commitfest?
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade if 'postgres' database is dropped