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 CEFA43A4B7F for ; Fri, 21 Jan 2005 15:41:01 +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 31643-05 for ; Fri, 21 Jan 2005 15:40:47 +0000 (GMT) Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id 6E2AF3A4AC4 for ; Fri, 21 Jan 2005 15:40:51 +0000 (GMT) Received: from [192.168.1.20] (clbb-248.saw.net [64.146.135.248]) (authenticated bits=0) by hosting.commandprompt.com (8.12.8/8.12.8) with ESMTP id j0LFepa8021883; Fri, 21 Jan 2005 07:40:51 -0800 Message-ID: <41F12289.1070104@commandprompt.com> Date: Fri, 21 Jan 2005 07:40:57 -0800 From: "Joshua D. Drake" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Clark 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> In-Reply-To: <41F0C858.7070508@ymogen.net> Content-Type: multipart/mixed; boundary="------------040302060603050206030805" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.029 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/384 X-Sequence-Number: 10074 This is a multi-part message in MIME format. --------------040302060603050206030805 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 > > > > Tatsuo Ishii wrote: > >> Can I ask a question? >> >> Suppose table A gets updated on the master at time 00:00. Until 00:03 >> pgpool needs to send all queries regarding A to the master only. My >> question is, how can pgpool know a query is related to A? >> -- >> Tatsuo Ishii >> >> >> > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL --------------040302060603050206030805 Content-Type: text/x-vcard; charset=utf-8; name="jd.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="jd.vcf" begin:vcard fn:Joshua Drake n:Drake;Joshua org:Command Prompt, Inc. adr:;;PO Box 215 ;Cascade Locks;OR;97014;US email;internet:jd@commandprompt.com title:Consultant tel;work:503-667-4564 tel;fax:503-210-0334 x-mozilla-html:FALSE url:http://www.commandprompt.com version:2.1 end:vcard --------------040302060603050206030805--