Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL clustering VS MySQL clustering

From: Matt Clark <matt(at)ymogen(dot)net>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: 2005-01-21 09:16:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
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.

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

In response to


pgsql-performance by date

Next:From: Andrei BintintanDate: 2005-01-21 09:20:48
Subject: Re: [SQL] OFFSET impact on Performance???
Previous:From: Matt CastersDate: 2005-01-21 08:50:46
Subject: Re:

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group