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