Re: Unable to create oracle_fdw (foreign data wrapper) extension

From: Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>
To: Arun Rangarajan <arunrangarajan(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: Scott Mead <scottm(at)openscg(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unable to create oracle_fdw (foreign data wrapper) extension
Date: 2016-09-16 15:43:37
Message-ID: 14adfd20-9503-f547-8b52-1c6552abfd5a@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 16.09.2016 17:01, Arun Rangarajan wrote:
> Hi Laurenz,
>
> Thanks for your reply.
>
> Sorry for the double posting here and StackOverflow
> http://stackoverflow.com/questions/39518417/unable-to-create-oracle-fdw-extension-on-postgres .
>
> I will update the details on StackOverflow since formatting and editing are easier there.
>
> On Fri, Sep 16, 2016 at 3:14 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at <mailto:laurenz(dot)albe(at)wien(dot)gv(dot)at>> wrote:
>
> Arun Rangarajan wrote:
> > But when I try to create the extension, I get the following error:
> >
> > postgres=# create extension oracle_fdw;
> > server closed the connection unexpectedly
> > This probably means the server terminated abnormally
> > before or while processing the request.
> > The connection to the server was lost. Attempting reset: Failed.
>
> > t=2016-09-15 16:16:08 PDT d= h= p=25327 a=LOG: 00000: server process (PID 20397) was terminated by signal 11: Segmentation fault
>
> Well, as I told you, get a stack trace with debugging symbols.
>
> Yours,
> Laurenz Albe
>
>

Hi!
May be this helps:

"Don't add oracle_fdw to shared_preload_libraries! (c) Laurenz Albe

Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2016-09-16 18:22:35 Re: PostgreSQL installation failure
Previous Message Tom Lane 2016-09-16 14:29:52 Re: performance problems with bulk inserts/updates on tsrange with gist-based exclude constrains