From: | Li Japin <japinli(at)hotmail(dot)com> |
---|---|
To: | "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-23 04:26:12 |
Message-ID: | SL2PR06MB3002DB9BC85058AAE4FB387CB6230@SL2PR06MB3002.apcprd06.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/23/19 12:09 PM, Tom Lane wrote:
> AFAICT they're harmless, so my advice is just ignore them.
>
> If you're sufficiently annoyed by them to find the cause
> and try to fix it, go ahead, but I haven't heard anyone
> else worried about it. It might be that SmartOS wants
> something like what we have to do on macOS and AIX,
> ie provide the core postgres executable in some sort of
> linker switch while linking shlibs that will be loaded
> by that executable.
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.
regards,
Japin Li
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2019-04-23 04:26:45 | Re: speeding up planning with partitions |
Previous Message | Tom Lane | 2019-04-23 04:09:52 | Re: Symbol referencing errors |