Re: Commitfest 2019-07, the first of five* for PostgreSQL 13 - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Commitfest 2019-07, the first of five* for PostgreSQL 13
Date
Msg-id CABUevEyQfYRR7CHgF+f2aPvZkkK72EuDwH1j08abxk3wBmhz=g@mail.gmail.com
Whole thread Raw
In response to Re: Commitfest 2019-07, the first of five* for PostgreSQL 13  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers


On Sat, Jun 29, 2019 at 10:05 AM Thomas Munro <thomas.munro@gmail.com> wrote:
On Sat, Jun 29, 2019 at 9:47 AM David Steele <david@pgmasters.net> wrote:
> On 6/28/19 1:15 PM, Tom Lane wrote:
> > Stephen Frost <sfrost@snowman.net> writes:
> >> shhhhh, don't look now, but there might be a "Resend email" button in
> >> the archives now that you can click to have an email sent to you...
> >
> > Oooh, lovely.
> >
> >> (thank you Magnus)
> >
> > +many
>
> Thank you, Magnus, this is really helpful!

Thanks, that's great news.  So, just to recap for new people who want
to get involved in testing and reviewing, the steps are:

1.  Subscribe to the pgsql-hackers mailing list, starting here:
https://lists.postgresql.org/
2.  In the process of doing that, you'll create a PostgreSQL community account.
3.  Choose a patch you're interested in from
https://commitfest.postgresql.org/23/ , and possibly add yourself as a
reviewer.
4.  Follow the link to the email thread.
5.  Click on the shiny new "Resend email" link on the latest email in
the thread to receive a copy, if you didn't have it already.
6.  You can reply-all to that email to join the discussion.

(As with all busy mailing lists, you'll probably want to set up
filtering to put pgsql-hackers messages into a seperate folder/label
due to volume.)

It might also be worth noticing that for those who only care about following one thread, you can subscribe to the pgsql-hackers list and then disable mail delivery. That way you can still post on the thread, and the PostgreSQL convention to use "reply all" on emails and directly CC all participants will ensure you get a copy of any replies. This does assume you either started the thread or at some point interacted with it of course -- otherwise your email address wouldn't be in the CC list.

--

pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Avoid full GIN index scan when possible
Next
From: Tomas Vondra
Date:
Subject: Re: Avoid full GIN index scan when possible