From: | Asko Oja <ascoja(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Ian Sollars <ian(dot)sollars(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: dblink syntax question for remotely invoking void-returning procedures |
Date: | 2009-01-26 16:53:47 |
Message-ID: | ecd779860901260853y40f60356xc25c713be76a0b2e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Take a stab at plproxy if you want to remotly call functions. Should be much
better suited than dblink for that.
Regards
Asko
On Mon, Jan 26, 2009 at 4:07 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On 1/24/09, Ian Sollars <ian(dot)sollars(at)gmail(dot)com> wrote:
> > Hello everyone,
> >
> > I've got some questions about dblink that I couldn't find answers to in
> the
> > documentation. Any help would be much appreciated.
> >
> > I need to invoke a function on a remote server that returns either void
> or
> > text, and I'm trying to find a nice way of doing it.
> >
>
> did you try this?
> perform * from dblink('test', 'select inserttest()') as t1(test text);
>
> Anyways, I never write void returning functions. Another problem with
> them (for example) is that they can't be called using the binary query
> protocol. These are minor nits since the workaround is easy.
>
> merlin
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | dave sale | 2009-01-26 17:13:05 | Unable to open DB: 2 Errors (unexpected zero page + could not open relation with OID) |
Previous Message | Tom Lane | 2009-01-26 15:36:34 | Re: where (x, y, z) in ((x1, y1, z1), (x1, y1, z1), (x1, y1, z1), (x2, y2, z2)) (not) optimized |