Re: PostgreSQL clustering VS MySQL clustering
| От | Josh Berkus |
|---|---|
| Тема | Re: PostgreSQL clustering VS MySQL clustering |
| Дата | |
| Msg-id | 200501211634.39560.josh@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL clustering VS MySQL clustering ("Peter Darley" <pdarley@kinesis-cem.com>) |
| Ответы |
Re: PostgreSQL clustering VS MySQL clustering
|
| Список | pgsql-performance |
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
В списке pgsql-performance по дате отправления: