Query

"Shaunak Godbole" <shaunak.godbole@gmail.com> writes:

I there a way of accessing other backends through the master backend.

It seems you're trying to reinvent contrib/dblink.

regards, tom lane

Ühel kenal päeval, E, 2007-04-09 kell 10:56, kirjutas Tom Lane:

"Shaunak Godbole" <shaunak.godbole@gmail.com> writes:

I there a way of accessing other backends through the master backend.

It seems you're trying to reinvent contrib/dblink.

Or you may want to use pl/proxy
( https://developer.skype.com/SkypeGarage/DbProjects/PlProxy ) which can
be used for data partitioning between different hosts/backends if the
interface to data is postgresql functions.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com

Hi,

As a part of my university project, I am trying to modify the postgres code
to support parallel system.

As the first step I have partitioned the data on different processors. And
have kept a master node to process all the query requests. Whenever my
master node is queried I need to push my query onto the backend processors.
For this I need a way of connect to different backends via my master node's
backend.

I have tried different functions like:
do_connect
SendQuery
PQconnectdb
etc.

But all of them give the same compilation error of not being able to find
the reference to the functions. Now if I include command.o and
common.opresent in src/bin/psql, I get the error of not referencing
other functions.

I there a way of accessing other backends through the master backend.

Thanks & Regards,
Shaunak Godbole

dblink is written specially for remote database access and is efficiently
written for postgresql and is also having async query capabilities, u may
check dblink_connect, dblink_fetch, dblink_exec, dblink_send_query, etc
..... more than that it is also having replication mechanism which u can
achieve using dblink_build_sql_insert, dblink_build_sql_delete,
dblink_build_sql_update which i think would be of utmost help if there is
some replication requirement in ur parallel database system

regards
nags
IIT Bombay
--
View this message in context: http://www.nabble.com/Query-tf3547482.html#a9954956
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.