X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EBBDE3A4BD0 for ; Fri, 21 Jan 2005 16:05:23 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 39262-06 for ; Fri, 21 Jan 2005 16:05:18 +0000 (GMT) Received: from ns1.turtle-entertainment.de (ns1.turtle-entertainment.de [193.41.200.20]) by svr1.postgresql.org (Postfix) with ESMTP id A8FC73A4BAC for ; Fri, 21 Jan 2005 16:05:15 +0000 (GMT) Received: from ip96.85.1311c-cud12k-02.ish.de ([62.143.85.96] helo=mail.office.turtle-entertainment.de) by ns1.turtle-entertainment.de with asmtp (Exim 3.22 #3 (Debian)) id 1Cs1HL-0003PL-00; Fri, 21 Jan 2005 17:04:55 +0100 Received: from [212.6.194.211] (helo=[212.6.194.211]) by mail.office.turtle-entertainment.de with asmtp (Exim 3.22 #7 (Debian)) id 1Cs1HK-000205-00; Fri, 21 Jan 2005 17:04:54 +0100 Message-ID: <41F12828.3090309@turtle-entertainment.de> Date: Fri, 21 Jan 2005 17:04:56 +0100 From: Bjoern Metzdorf User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Joshua D. Drake" Cc: Matt Clark , Tatsuo Ishii , pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering References: <200501200929.37228.darcy@wavefire.com> <20050121.104007.74755729.t-ishii@sra.co.jp> <200501201949.24292.josh@agliodbs.com> <20050121.170731.08315885.t-ishii@sra.co.jp> <41F0C858.7070508@ymogen.net> <41F12289.1070104@commandprompt.com> In-Reply-To: <41F12289.1070104@commandprompt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.842 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200501/385 X-Sequence-Number: 10075 Joshua D. Drake wrote: > Matt Clark wrote: > >> Presumably it can't _ever_ know without being explicitly told, because >> even for a plain SELECT there might be triggers involved that update >> tables, or it might be a select of a stored proc, etc. So in the >> general case, you can't assume that a select doesn't cause an update, >> and you can't be sure that the table list in an update is a complete >> list of the tables that might be updated. > > > Uhmmm no :) There is no such thing as a select trigger. The closest you > would get > is a function that is called via select which could be detected by > making sure > you are prepending with a BEGIN or START Transaction. Thus yes pgPool > can be made > to do this. SELECT SETVAL() is another case. I'd really love to see pgpool do this. I am also curious about Slony-II development, Tom mentioned a first meeting about it :) Regards, Bjoern