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 19:42:48
Message-ID: 87bm97srqj.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> However, the info I can find about this suggests that it's only
Tom> relevant for exported functions, not ones that are hidden by means
Tom> of a version-script. Since libpq doesn't export pg_saslprep, this
Tom> shouldn't be happening?

Tom> But wait, this problem is being reported on OpenBSD. I wonder
Tom> whether their linker behaves anything like Linux's ... hm, it
Tom> looks like it *is* the same linker.

But the makefile is not doing the same thing. SHLIB_EXPORTS looks like
it's being ignored on every platform except linux, macos and windows in
Makefile.shlib.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message André Hänsel 2018-09-08 19:43:18 AW: BUG #15373: null / utf-8
Previous Message Michael Paquier 2018-09-08 19:39:14 Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables