Hello,
We are expecting to release pgpool-II 2.3 within November. New
features include:
- Adopt PostgreSQL 8.4 parser. On of the visible effects of this is,
WITH clause can be load balanced.
- Allow to use INSERT/UPDATE including CURRENT_TIME_STAMP,
CURRENT_DATE, now(). pgpool-II guarantees that each DB node will be
populated exactly same value for these data type. For example
consider following table:
CREATE TABLE t1(id INTEGER PRIMARY KEY, regdate TIMESTAMP DEFAULT
CURRENT_TIMESTAMP);
Let's populate t1:
INSERT INTO t1(id) VALUES(1);
Actual query executed by pgpool-II is:
INSERT INTO "t1"("id", "regdate") VALUES (1,'2009-11-15 21:35:01.783053+09');
'2009-11-15 21:35:01.783053+09' is extraced from PostgreSQL by
executing SELECT CURRENT_TIMESTAP. So t1 tables on all DB nodes has
exactly same value.
- Add new directive log_per_node_statement. If true, print all
statements to the log. Similar to log_statement except that prints
DB node id and backend process id info. Example:
2009-11-15 21:34:12 LOG: pid 22285: DB node id: 0 backend pid: 22301
statement: CREATE TABLE t1(id INTEGER PRIMARY KEY, regdate TIMESTAMP DEFAULT
CURRENT_TIMESTAMP);
2009-11-15 21:34:12 LOG: pid 22285: DB node id: 1 backend pid: 22300
statement: CREATE TABLE t1(id INTEGER PRIMARY KEY, regdate TIMESTAMP DEFAULT
CURRENT_TIMESTAMP);
Users who are interested in these features are encouraged to try CVS
HEAD. Please feel free to ask me if you are not sure how to get CVS
HEAD source.
Also we are welcome if you have usefull patches to add/enhance
pgpool-II. Since this is a major version up, this is the good chance
to add/change features. I myself think about to add more
features. Stay tuned...
--
Tatsuo Ishii
SRA OSS, Inc. Japan
_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general
