From: Joe Conway <mail@joeconway.com>
To: Frankie Lam <frankie@ucr.com.hk>
Cc: pgsql-sql@postgresql.org
Subject: Re: dblink question please
Date: Wed, 12 Feb 2003 21:22:45 -0800
Message-ID: <3E4B2BA5.3020409@joeconway.com> (raw)
In-Reply-To: <b2f73m$2skf$1@news.hub.org>
References: <b2etmt$26en$1@news.hub.org>
<b2f73m$2skf$1@news.hub.org>
Frankie Lam wrote:
> Yah!
>
> That's exactly what I did already(did this to all lines containing
> `elog(ERROR...)'. :-D
> But, I'm still experiencing some error messages when I'm doing 'extreme'
> test to
> plpgsql functions,
> for example 'ExecMakerTableFunctionResult: Invalid result from function
> returning tuple'.
>
> I really have no idea about what this message is related to the dblink
> functions. Any idea
> about it? Thanks so much.
Sounds like you didn't heed my warning. It is *probably* safe to make
the elog(ERROR...) to elog(NOTICE...) change *in that one function*,
dblink_connect(), and then use persistent connections, e.g.
select dblink_connect('dbname=blah ...');
select * from dblink('select f1 from foo') as (f1 text);
If instead you made the change within the dblink_record() function, and
you weren't careful to add additional error handling, then the message
you got is what I'd expect. You basically broke dblink for those scenarios.
Joe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mail@joeconway.com, frankie@ucr.com.hk
Subject: Re: dblink question please
In-Reply-To: <3E4B2BA5.3020409@joeconway.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox