pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matt Clark <matt@ymogen.net>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Fri, 21 Jan 2005 17:35:13 +0000
Message-ID: <41F13D51.9070608@ymogen.net> (raw)
In-Reply-To: <41F12289.1070104@commandprompt.com>
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>

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
>
>
>



view thread (131+ messages)  latest in thread

Message-ID: <41F13D51.9070608@ymogen.net>
Permalink:  ../41F13D51.9070608@ymogen.net/
Also on:    postgresql.org/message-id/41F13D51.9070608@ymogen.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: matt@ymogen.net, jd@commandprompt.com, t-ishii@sra.co.jp
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <41F13D51.9070608@ymogen.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox