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 B26D23A4C10 for ; Fri, 21 Jan 2005 17:35:38 +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 62041-03 for ; Fri, 21 Jan 2005 17:35:24 +0000 (GMT) Received: from bayswater1.ymogen.net (unknown [217.27.247.154]) by svr1.postgresql.org (Postfix) with ESMTP id 51F1B3A4BEC for ; Fri, 21 Jan 2005 17:35:15 +0000 (GMT) Received: from [82.68.132.234] (82-68-132-234.dsl.in-addr.zen.co.uk [82.68.132.234]) by bayswater1.ymogen.net (Postfix) with ESMTP id A2260A6640; Fri, 21 Jan 2005 17:35:13 +0000 (GMT) Message-ID: <41F13D51.9070608@ymogen.net> Date: Fri, 21 Jan 2005 17:35:13 +0000 From: Matt Clark User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Joshua D. Drake" Cc: 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=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/392 X-Sequence-Number: 10082 Yes, I wasn't really choosing my examples particularly carefully, but I think the conclusion stands: pgpool (or anyone/thing except for the server) cannot in general tell from the SQL it is handed by the client whether an update will occur, nor which tables might be affected. That's not to say that pgpool couldn't make a good guess in the majority of cases! M 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. > > Sincerely, > > Joshua D. Drake > > >