Re: Symbol referencing errors

From: Li Japin <japinli(at)hotmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Symbol referencing errors
Date: 2019-04-24 07:33:44
Message-ID: SL2PR06MB30025B8C7427124F4417105DB63C0@SL2PR06MB3002.apcprd06.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Finally, I find this crash is caused by shmget_osm, which does not support SmartOS (maybe,
I am not sure). When I install Oracle Instant Client 12.2.0.1.0, it works.

https://github.com/laurenz/oracle_fdw/issues/313

On 4/23/19 3:09 PM, Laurenz Albe wrote:

On Tue, 2019-04-23 at 04:26 +0000, Li Japin wrote:

Yes, those errors does not impact the postgresql, but when
I use oracle_fdw extension, I couldn't startup the postgresql,
and I find that the dlopen throw an error which lead postmaster
exit, and there is not more information.

That may wall be a bug in oracle_fdw, since I have no reports of
anybody running it on that operating system.

Maybe you should open an oracle_fdw issue, but I don't know how
much I can help you, since this is the first time I have heard
of SmartOS.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2019-04-24 07:36:27 Re: pg_dump partitions can lead to inconsistent state after restore
Previous Message David Fetter 2019-04-24 06:26:23 Re: [PATCH v1] Show whether tables are logged in \dt+