Re: Fast Default WIP patch for discussion - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: Fast Default WIP patch for discussion
Date
Msg-id 832c53a6-1625-2f44-5ba6-dccec66e9b51@2ndquadrant.com
Whole thread Raw
In response to Re: Fast Default WIP patch for discussion  (Serge Rielau <serge@rielau.com>)
List pgsql-hackers
Hi,

On 26/10/16 18:22, Serge Rielau wrote:
> Euler,
> 
> Thanks, I was previously told I should post a WIP patch here.
> There are too many open issues to be near committing.
> Anyway, I have created a patch. 
> https://commitfest.postgresql.org/11/843/#

Adding to commitfest is act of asking for review, it does not mean it's
committable.

> Since this is my first time I do have a couple of questions:
> There are entries for a git and a wiki link.
> Should I push the patch to some branch, if so which repository?
>

That's optional, mostly useful for bigger (or complex) patches or
patches where there is code cooperation between multiple people. Wiki
page for patch sometimes contains basically what your first email said.

BTW it's customary to bottom post, not top post on this list.

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: emergency outage requiring database restart
Next
From: Gilles Darold
Date:
Subject: Re: Patch to implement pg_current_logfile() function