From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Add WL_EXIT_ON_PM_DEATH pseudo-event. |
Date: | 2018-11-25 17:56:22 |
Message-ID: | 9911.1543168582@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> Fix pushed.
> By way of penance, I have now configured PG_TEST_EXTRA="ssl ldap
> kerberos" for my build farm animals elver and eelpout. elver should
> pass at the next build, as I just tested it with --nosend, but eelpout
> is so slow I'll just take my chances see if that works.
Nope :-(. Looks like something about key length ... probably just
misconfiguration?
> I'll also
> review the firewall config on those VMs, since apparently everyone is
> too chicken to run those tests, perhaps for those sorts of reasons.
I think in many cases the answer is just "it's not in the default
buildfarm configuration". I couldn't think of a strong reason not
to run the ssl check on longfin, so I've just updated that to do so.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-11-25 20:53:19 | Re: pgsql: Add WL_EXIT_ON_PM_DEATH pseudo-event. |
Previous Message | Peter Eisentraut | 2018-11-25 15:49:23 | pgsql: Integrate recovery.conf into postgresql.conf |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2018-11-25 17:57:15 | Re: Don't wake up to check trigger file if none is configured |
Previous Message | Pavel Stehule | 2018-11-25 17:28:05 | Re: Desirability of client-side expressions in psql? |