Re: pgsql: Implement channel binding tls-server-end-point for SCRAM

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Implement channel binding tls-server-end-point for SCRAM
Date: 2018-01-08 15:44:11
Message-ID: CANP8+j+aJr9o1i_RbNcVwXxU6y5pncpyfGG-CbAwwdAFU7tMiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 4 January 2018 at 21:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Implement channel binding tls-server-end-point for SCRAM
>
> Buildfarm doesn't like this one bit.

Can't we automate these messages? Seems strange to send manual emails
every time. We do know who the commits are coming from and we have
their email address.

It would be useful to get automatic message giving a summary of
buildfarm results at 15, 30 and 60 minute intervals, even if it is
just ALL CLEAR.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-01-08 16:01:53 Buildfarm status monitoring (was Re: pgsql: Implement channel binding tls-server-end-point for SCRAM)
Previous Message Michael Paquier 2018-01-08 13:14:11 Re: pgsql: Implement channel binding tls-server-end-point for SCRAM

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-01-08 15:58:13 Re: Parallel append plan instability/randomness
Previous Message Robert Haas 2018-01-08 15:43:00 Re: Invalid pg_upgrade error message during live check