[HACKERS] WIP: Fix parallel workers connection bug in pg_dump (Bug #13727)

Parallel workers were failing to connect to the database when running pg_dump with a connection string. The first of the following two commands runs without errors, while the second one fails: pg_dump "postgres://my-user:my-passw...@my.hostname.com:5432/my-db" -Fd -f my-dump pg_dump

Re: [HACKERS] WIP: Fix parallel workers connection bug in pg_dump (Bug #13727)

I'm still unclear on how to write regression tests for a connectivity bug. Are they necessary in this case? On Sun, Oct 25, 2015 at 5:55 PM, Zeus Kronion <zkron...@gmail.com> wrote: > Parallel workers were failing to connect to the database when running > pg_dump with a conne

Re: [HACKERS] WIP: Fix parallel workers connection bug in pg_dump (Bug #13727)

On Nov 1, 2015 5:04 PM, "Marko Tiikkaja" <ma...@joh.to> wrote: > > On 10/25/15 10:55 PM, Zeus Kronion wrote: >> >> Parallel workers were failing to connect to the database when running >> pg_dump with a connection string. The first of the following tw

[HACKERS] Possible SSL improvements for a newcomer to tackle

I previously made one minuscule contribution to the project two years ago. I'm interested in doing some more, and I'm trying to figure out what to focus on. Two SSL-related projects caught my attention: 1) Allow automatic selection of SSL client certificates from a certificate store

Re: [HACKERS] Possible SSL improvements for a newcomer to tackle

On Tue, Oct 3, 2017 at 11:39 AM, Nico Williams wrote: > On Tue, Oct 03, 2017 at 12:33:00AM -0400, Tom Lane wrote: > > So to default to verification would be to default to failing to > > connect at all until user has created a ~/.postgresql/root.crt file with > > valid,