Re: dblink() from GridSQL - Mailing list pgsql-general

From Scott Mead
Subject Re: dblink() from GridSQL
Date
Msg-id BANLkTin=tfk_PNUUjJabfrDCWUx28yLg5A@mail.gmail.com
Whole thread Raw
In response to Re: dblink() from GridSQL  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: dblink() from GridSQL  (Sam Nelson <samn@consistentstate.com>)
List pgsql-general

On Thu, May 5, 2011 at 1:40 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
On Thu, May 5, 2011 at 12:13 PM, Sam Nelson <samn@consistentstate.com> wrote:
> Hi List,
> We have a customer who is trying to migrate a few PostgresPlus instances to
> GridSQL clusters.  They have a process that pulls data from another server
> using dblink every night, and we're trying to replicate that on the GridSQL
> instance, but grid is being a bit of a pain.
> Grid doesn't seem to allow functions in from statements, and, of course, it
> spits out errors about functions returning records being called in the wrong
> context if we just try "select dblink(foo, bar);" (we had to try it).
> Has anyone else run into this specific issue?

GridSQL itself doesn't support functions. 
 
 Is there a known workaround?
>  Any ideas on what else we should try?


You'd have to present the data to be partitioned to the gsql controller for partitioning to happen properly, or use the high-speed import that it comes with.  Could you dump the data to an intermediary csv and then push it at the import utility?

--Scott
 
have you considered wrapping the output of the dblink query in a view?

merlin

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: dblink() from GridSQL
Next
From: jtkells@verizon.net
Date:
Subject: psql tunneling thru a middle server