From: Michael Paquier <michael@paquier.xyz>
To: code@jeremyevans.net
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables
Date: Thu, 6 Sep 2018 14:58:36 -0700
Message-ID: <20180906215836.GP2726@paquier.xyz> (raw)
In-Reply-To: <153626613985.23143.4743626885618266803@wrigleys.postgresql.org>
References: <153626613985.23143.4743626885618266803@wrigleys.postgresql.org>
On Thu, Sep 06, 2018 at 08:35:39PM +0000, PG Bug reporting form wrote:
> If necessary I can build a debug version of PostgreSQL and try using that in
> production so I can get a better backtrace if it crashes again. However,
> considering that the crash is rare in my environment, it's unlikely I will
> be able to produce a better backtrace for the error quickly.
That would be nice. From what I can see this would be a race condition,
which is not obvious by looking at the code. Testing with a two-node
deployment where the first node has a foreign table which connects to a
second node, using SCRAM authentication, holding the physical table,
then doing many foreign scans across many clients don't show any
problem. Did libpq complain at some point in the session where the
crash happened about any error?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, code@jeremyevans.net, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables
In-Reply-To: <20180906215836.GP2726@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox