Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeremy Evans <code(at)jeremyevans(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables
Date: 2018-09-08 13:22:22
Message-ID: 87o9d8rv08.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

Tom> Could it be that somehow, when libpq is loaded into the backend
Tom> address space as it is here, libpq winds up calling the backend's
Tom> copy of pg_saslprep rather than its own?

Yes, that is a thing that happens with ELF-style shared libs when you
dynamically load shared libraries that weren't linked with -Bsymbolic.

Is this potentially also a problem for libpqwalreceiver, which also
loads libpq?

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2018-09-08 16:01:09 Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
Previous Message Tom Lane 2018-09-08 12:34:15 Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables