Re: problem with dblink and "drop owned by" - Mailing list pgsql-general

From James W. Wilson
Subject Re: problem with dblink and "drop owned by"
Date
Msg-id CAFP0EzJKcM5NTCUbisc92e=E72b1P60yHdPawqwf9cJEqV8O5g@mail.gmail.com
Whole thread Raw
In response to Re: problem with dblink and "drop owned by"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: problem with dblink and "drop owned by"
List pgsql-general
I'm confused. I thought foreign data wrappers were required to create
database links from one Postgresql server to another. Is there some
way to create a database link without using them? I was working off of
this example:

http://www.postgresql.org/docs/8.4/static/contrib-dblink-connect.html

I'm stuck with 8.4 for now, unfortunately.

James

On Wed, Jul 18, 2012 at 6:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "James W. Wilson" <jww1066@gmail.com> writes:
>> Hi, I'm using Postgresql 8.4.12-1 on Debian. I've installed 'dblink'
>> from the contrib package (also 8.4.12-1) and am now running into a
>> strange problem when I run "drop owned by".
>
> You're running into a old bug, which is that DROP OWNED BY doesn't know
> what to do with foreign data wrappers.  According to the commit logs,
> this was fixed a couple of years ago in 9.0 and up, but we did not
> bother to fix 8.4 because foreign data wrappers aren't actually useful
> for anything in 8.4.  If you want to work with FDWs, I'd suggest moving
> forward to a release where they have some real functionality ...
>
>                         regards, tom lane

pgsql-general by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [BUGS] main log encoding problem
Next
From: rajonrole@gmail.com
Date:
Subject: data from the table is getting dropped when I am restarting my application after making changes in the objects created in my application in play