Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 276D0650EF3 for ; Mon, 30 Jun 2008 10:52:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 83228-02 for ; Mon, 30 Jun 2008 10:51:45 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.248]) by postgresql.org (Postfix) with ESMTP id A2D6E650FE1 for ; Mon, 30 Jun 2008 10:34:32 -0300 (ADT) Received: by hs-out-0708.google.com with SMTP id x43so270823hsb.3 for ; Mon, 30 Jun 2008 06:34:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=RV1KXrFUDxOAfvE3o6BwSH9MpmGdvFHpZXf0Cz3MXhE=; b=mIMyF6sPaX4gm+o7St7QtvLsIhBTr24+w7IOiKYpgf81jgN/zzZGn42ZM5Gp7Ez7c+ C5WizNb7zd0+OyFayMnWplDpZDTcymgD2iuzMRQZQ7nIdkycbkNpIyGg8Y0R0nvj+Vb9 JGC8UFTLAoukkZqeCuCVPrHRoCizT9wDX4mA8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=fZEacex4RRIGPj3ldcVCRmW9UetMkaRDD7bSEVgq5Cwe+Gh60nNvGs9r1+GdeudLH0 CNGEwdbkHDQpHBuC1fiC1YaGQUikHPG7pH2ps75PQa0ZtsR305TFwuTuZY1UyVlWR5DH ZoApzmfRrVlOIY8tEGvGmMSc2r9spEN9KxMp4= Received: by 10.150.201.2 with SMTP id y2mr8413276ybf.225.1214832867542; Mon, 30 Jun 2008 06:34:27 -0700 (PDT) Received: by 10.150.186.15 with HTTP; Mon, 30 Jun 2008 06:34:27 -0700 (PDT) Message-ID: <36e682920806300634y10a34fc1vfa9b18658d8e857b@mail.gmail.com> Date: Mon, 30 Jun 2008 09:34:27 -0400 From: "Jonah H. Harris" To: "Marko Kreen" Subject: Re: Federated Postgresql architecture ? Cc: "Chris Browne" , pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200806261441.12413.josh@agliodbs.com> <36e682920806261440o2142783blbc38013f4f5677c2@mail.gmail.com> <200806261531.03892.josh@agliodbs.com> <60zlp6zqsm.fsf@dba2.int.libertyrms.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/234 X-Sequence-Number: 30584 On Mon, Jun 30, 2008 at 9:16 AM, Marko Kreen 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/