Horton

Re: BUG #16604: pg_dump with --jobs breaks SSL connections

Magnus Hagander <magnus@hagander.net>

View thread View on postgr.es
From: Magnus Hagander <magnus@hagander.net>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: zsolt.ero@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2020-09-15T12:04:09Z
Lists: pgsql-bugs 
On Tue, Sep 15, 2020 at 1:36 PM Daniel Gustafsson <daniel@yesql.se> wrote:

> > On 1 Sep 2020, at 22:08, PG Bug reporting form <noreply@postgresql.org>
> wrote:
> >
> > The following bug has been logged on the website:
> >
> > Bug reference:      16604
> > Logged by:          Zsolt Ero
> > Email address:      zsolt.ero@gmail.com
> > PostgreSQL version: 12.4
> > Operating system:   Ubuntu 20.04
> > Description:
> >
> > I'm using pg_dump in the following syntax:
> >
> > pg_dump --dbname="sslmode=verify-ca sslrootcert=server-ca.pem \
> >      sslcert=client-cert.pem sslkey=client-key.pem \
> >      hostaddr=1.2.3.4 \
> >      user=postgres dbname=app" \
> >      --format=directory \
> >      --file=dump_app \
> >      --jobs=3
> >
> > As long as the --jobs parameter is present, the process breaks after
> > "pg_dump: saving database definition".
> > It breaks with "FATAL:  connection requires a valid client certificate".
> >
> > Without --jobs it completes without errors. I also think it's happening
> with
> > pg_restore as well.
>
> I am unable to reproduce this with 12.4 as well as 14devel.  If this error
> is
> reproducible for you, can you please share more details on the setup?
> (ideally
> a recipe for setting up a repro environment)
>

Grasping a long straw hwere, but I wonder if it could be relataed to the
debian/ubuntu wrapper.

Zsolt, can you try running it with hardcoding the pg_dump path
to /usr/lib/postgresql/12/bin/pg_dump instead of just pg_dump, to see if
that might be it?

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

Commits

  1. Fix connection string handling in psql's \connect command.

  2. Fix connection string handling in src/bin/scripts/ programs.

  3. Fix handling of -d "connection string" in pg_dump/pg_restore.