| From: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
|---|---|
| To: | Serge Rielau <serge(at)rielau(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fast Default WIP patch for discussion |
| Date: | 2016-10-26 22:08:55 |
| Message-ID: | 832c53a6-1625-2f44-5ba6-dccec66e9b51@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2016-10-26 22:31:56 | Re: Patch to implement pg_current_logfile() function |
| Previous Message | Andres Freund | 2016-10-26 20:48:55 | Re: emergency outage requiring database restart |