Re: problem with dblink and "drop owned by"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "James W(dot) Wilson" <jww1066(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Subject: Re: problem with dblink and "drop owned by"
Date: 2012-07-19 02:15:38
Message-ID: 8012.1342664138@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"James W. Wilson" <jww1066(at)gmail(dot)com> writes:
> I'm confused. I thought foreign data wrappers were required to create
> database links from one Postgresql server to another.

contrib/dblink doesn't require them. It does have an option to use an
FDW instead of a libpq connection string to specify the connection
target. I had forgotten that that option got added in 8.4, before we
had any other working use for FDWs --- so maybe we should rethink the
decision not to backport this fix?

Author: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
Branch: master Release: REL9_1_BR [e356743f3] 2010-11-12 15:29:23 +0200
Branch: REL9_0_STABLE Release: REL9_0_2 [533073cf2] 2010-11-12 15:30:19 +0200

Add missing support for removing foreign data wrapper / server privileges
belonging to a user at DROP OWNED BY. Foreign data wrappers and servers
don't do anything useful yet, which is why no-one has noticed, but since we
have them, seems prudent to fix this. Per report from Chetan Suttraway.
Backpatch to 9.0, 8.4 has the same problem but this patch didn't apply
there so I'm not going to bother.

In the meantime, though, you do not *need* an FDW. dblink worked fine
for many releases before FDWs existed, and it still does work without
'em.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2012-07-19 03:35:05 Odd corruption issue reported on dba.stackexchange.com, need advice
Previous Message Tatsuo Ishii 2012-07-19 01:57:27 Re: main log encoding problem