Re: [Q] single image Table across multiple PG servers

From: Kevin Kempter <kevink(at)consistentstate(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [Q] single image Table across multiple PG servers
Date: 2009-07-14 19:03:27
Message-ID: 200907141303.27399.kevink@consistentstate.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tuesday 14 July 2009 12:38:27 V S P wrote:
> Hi,
> thank you for the links
>
>
> I read through the presentation
>
> and they did not solve the issue for me -- which presenting a e
> table from multiple
> shards as one single table (at least for reads) for ODBC clients.
>
>
> I also do not think that skypetools do that
>
> they have implemented essentially an API on top of their shards
> (separate db servers)
> that does the table querying. That means that I have to write a
> separate API for every time
> a user decides on a new query.
>
>
> May be I misunderstood the approaches, but none of them actually
> figures out how to
> utilize the computing power/memory of multiple servers to satisfy
> requests that spawn across
> servers.
>
> I think Oracle supports the ability to at least reference a table
> in another server, I do not think
> PG does that
>
> It is possible that I have to look into the free DB2 server
> offering (as the free version is exactly meant
> to run on underpowered computers)
>
> I just wanted to ask the list first.
>
>
> thank you
>
>
> On Tue, 14 Jul 2009 13:04 +0530, "Ransika de Silva"
> <ransika(at)gmail(dot)com> wrote:
>
> Hello,
>
>
>
> We were also in search of having a table split across multiple
> databases but then found out about skypetools and at the same
> time the following
> article; [1]http://www.jurriaanpersyn.com/archives/2009/02/12/dat
> abase-sharding-at-netlog-with-mysql-and-php/, true that it's not
> done with PG, but the same thing can be done with PG as well.
>
>
>
> Assume this will be helpful for you.
>
>
>
> Regards,
>
> Ransika
>
> On Tue, Jul 14, 2009 at 4:20 PM, Scott Marlowe
> <[2]scott(dot)marlowe(at)gmail(dot)com> wrote:
>
> On Mon, Jul 13, 2009 at 11:16 PM, V S P<[3]toreason(at)fastmail(dot)fm>
>
> wrote:
> > Hello
> >
> > I am researching how to store the data for easy 'user-driven'
> > reporting (where I do not need to develop application for
> > every user request).
> >
> > The data will typically be number ranges and text strings with
> > unique Id for each row
> >
> > I hope there will be a lot of data :-).
> >
> > So in that anticipation I am looking for a way
> > to allow
> > SQL/ODBC access to the data
> >
> > but in a way that each table resides on more than one
> > PG server
> >
> > for example:
> >
> > table 1 lives in 3 PG instances (I can partition the data by
>
> date range)
>
> > table 2 lives in the same 3 instances plus another one (because
>
> it's
>
> > bigger)
> >
> >
> > and I would like users to be able to issue SQL from within ODBC
>
> that
>
> > joins them.
>
> I think that skype's skytools could be used to create such a
> solution,
> in particular pl/proxy.
>
>
> --
> Sent via pgsql-general mailing list
> ([4]pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> [5]http://www.postgresql.org/mailpref/pgsql-general
>
> --
> Ransika De Silva
> SCMAD 1.0, SCJP 1.4,
> BSc.(Hons) Information Systems
>
> References
>
> 1.
> http://www.jurriaanpersyn.com/archives/2009/02/12/database-sharding-at-netl
>og-with-mysql-and-php/ 2. mailto:scott(dot)marlowe(at)gmail(dot)com
> 3. mailto:toreason(at)fastmail(dot)fm
> 4. mailto:pgsql-general(at)postgresql(dot)org
> 5. http://www.postgresql.org/mailpref/pgsql-general
> --
> Vlad P
> author of C++ ORM http://github.com/vladp/CppOrm/tree/master

Maybe this is what you're looking for?

http://www.enterprisedb.com/community/projects/gridsql.do

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Kempter 2009-07-14 19:45:11 Re: [Q] single image Table across multiple PG servers
Previous Message Alvaro Herrera 2009-07-14 19:03:04 Re: [GENERAL] large object does not exist after pg_migrator