pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonah H. Harris <jonah.harris@gmail.com>
To: Marko Kreen <markokr@gmail.com>
Cc: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Federated Postgresql architecture ?
Date: Mon, 30 Jun 2008 09:34:27 -0400
Message-ID: <36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.com> (raw)
In-Reply-To: <e51f66da0806300616q47a3433bt52f78716427c5665@mail.gmail.com>
References: <C401CB24-5BD6-455B-A62B-9D737E44CEB3@kevinkempterllc.com>
	<200806261441.12413.josh@agliodbs.com>
	<36e682920806261440o2142783blbc38013f4f5677c2@mail.gmail.com>
	<200806261531.03892.josh@agliodbs.com>
	<60zlp6zqsm.fsf@dba2.int.libertyrms.com>
	<e51f66da0806300616q47a3433bt52f78716427c5665@mail.gmail.com>

On Mon, Jun 30, 2008 at 9:16 AM, Marko Kreen <markokr@gmail.com> wrote:
> But I want to clarify it's goal - it is not to run "pre-determined
> queries."  It is to run "pre-determined complex transactions."

Yes.

> And to make those work in a "federated database" takes huge amount
> of complexity that PL/Proxy simply sidesteps.  At the price of
> requiring function-based API.  But as the function-based API has
> other advantages even without PL/Proxy, it seems fine tradeoff.

Agreed.  PL/Proxy has its own set of advantages.

As usual, it really just depends on the application and its requirements.

-- 
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
Edison, NJ 08837 | http://www.enterprisedb.com/



view thread (9+ messages)

Message-ID: <36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.com>
Permalink:  ../36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.com/
Also on:    postgresql.org/message-id/36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: jonah.harris@gmail.com, markokr@gmail.com, cbbrowne@acm.org
  Subject: Re: Federated Postgresql architecture ?
  In-Reply-To: <36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.com>
  References: <C401CB24-5BD6-455B-A62B-9D737E44CEB3@kevinkempterllc.com> <200806261441.12413.josh@agliodbs.com> <36e682920806261440o2142783blbc38013f4f5677c2@mail.gmail.com> <200806261531.03892.josh@agliodbs.com> <60zlp6zqsm.fsf@dba2.int.libertyrms.com> <e51f66da0806300616q47a3433bt52f78716427c5665@mail.gmail.com> <36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.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