From: Josh Berkus <josh@agliodbs.com>
To: Peter Darley <pdarley@kinesis-cem.com>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: darcy@wavefire.com
Cc: jd@www.commandprompt.com
Cc: sfrost@snowman.net
Cc: herve@elma.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Fri, 21 Jan 2005 16:34:39 -0800
Message-ID: <200501211634.39560.josh@agliodbs.com> (raw)
In-Reply-To: <PDEOIIFFBIAABMGNJAGPMEOODLAA.pdarley@kinesis-cem.com>
References: <PDEOIIFFBIAABMGNJAGPMEOODLAA.pdarley@kinesis-cem.com>
Peter, Tatsuo:
would happen with SELECT queries that, through a function or some
> other mechanism, updates data in the database? Would those need to be
> passed to pgpool in some special way?
Oh, yes, that reminds me. It would be helpful if pgPool accepted a control
string ... perhaps one in a SQL comment ... which indicated that the
statement to follow was, despite appearances, an update. For example:
--STATEMENT_IS_UPDATE\n
The alternative is, of course, that pgPool direct all explicit transactions to
the master ... which is a good idea anyway. So you could do:
BEGIN;
SELECT some_update_function();
COMMIT;
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, pdarley@kinesis-cem.com, t-ishii@sra.co.jp, darcy@wavefire.com, jd@www.commandprompt.com, sfrost@snowman.net, herve@elma.fr
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <200501211634.39560.josh@agliodbs.com>
* 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