Skip site navigation (1) Skip section navigation (2)

Re: Add dblink function to check if a named connection exists

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tommy Gildseth <tommy(dot)gildseth(at)usit(dot)uio(dot)no>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add dblink function to check if a named connection exists
Date: 2008-06-02 00:14:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> Tommy Gildseth <tommy(dot)gildseth(at)usit(dot)uio(dot)no> writes:
>> One obvious disadvantage of this approach, is that I need to connect and 
>> disconnect in every function. A possible solution to this, would be 
>> having a function f.ex dblink_exists('connection_name') that returns 
>> true/false depending on whether the  connection already exists.
> Can't you do this already?
> 	SELECT 'myconn' = ANY (dblink_get_connections());
> A dedicated function might be a tad faster, but it probably isn't going
> to matter compared to the overhead of sending a remote query.

I agree. The above is about as simple as
   SELECT dblink_exists('dtest1');
and probably not measurably slower. If you still think a dedicated 
function is needed, please send the output of some performance testing 
to justify it.

If you really want the notational simplicity, you could use an SQL 
function to wrap it:

CREATE OR REPLACE FUNCTION dblink_exists(text)
RETURNS bool AS $$
   SELECT $1 = ANY (dblink_get_connections())
$$ LANGUAGE sql;

contrib_regression=# SELECT dblink_exists('dtest1');
(1 row)

I guess it might be worthwhile adding the SQL function definition to as an enhancement in 8.4.


In response to


pgsql-hackers by date

Next:From: David E. WheelerDate: 2008-06-02 03:53:25
Subject: Case-Insensitve Text Comparison
Previous:From: David FetterDate: 2008-06-01 23:33:55
Subject: == PostgreSQL Weekly News - June 01 2008 ==

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group