TODO - 版の履歴

Admin: マルチステートメントクエリ実装上の問題を追記。

2014-01-28T02:18:03Z

マルチステートメントクエリ実装上の問題を追記。

← 古い版		2014年1月28日 (火) 02:18時点における版
24行目:		24行目:
	: ドキュメントによると、 pgpool-II はマルチステートメントなクエリ (BEGIN;SELECT 1;END) を認識しません。 Pgpool-II は最初のクエリ（この場合は "BEGIN"）だけをパースし、処理を決定します。		: ドキュメントによると、 pgpool-II はマルチステートメントなクエリ (BEGIN;SELECT 1;END) を認識しません。 Pgpool-II は最初のクエリ（この場合は "BEGIN"）だけをパースし、処理を決定します。
	: もちろん、これは様々の問題を引き起こすでしょう。pgpool-II がマルチステートメントなクエリの各要素を理解できるようになると嬉しいです。		: もちろん、これは様々の問題を引き起こすでしょう。pgpool-II がマルチステートメントなクエリの各要素を理解できるようになると嬉しいです。
			: 実装上の問題は、マルチステートメントのバックエンドでの扱いにあります。たとえば、BEGIN;SELECT 1;ENDに対してバックエンドは、BEGIN、SELECT、ENDに対してそれぞれCommand Completeを返しますが、Ready for queryは最後に1度しか返しません。したがって、psqlのように単純にBEGIN, SELECT 1, END を分解しただけではうまく処理できません。

	=== レプリケーションモード時に、カーソルの宣言がロードバランスされずに全ての DB ノードに送信される ===		=== レプリケーションモード時に、カーソルの宣言がロードバランスされずに全ての DB ノードに送信される ===

Admin: 英文を和訳しました。

2013-12-09T11:06:17Z

英文を和訳しました。

差分を表示

2013年7月22日 (月) 07:49にIshiiによる

2013-07-22T07:49:52Z

← 古い版		2013年7月22日 (月) 07:49時点における版
61行目:		61行目:
	=== Put together a definition of error codes into a single header file ===		=== Put together a definition of error codes into a single header file ===
	: Currently most error codes used by pool_send_{error,fatal}_message() etc (e.g. "XX000", "XX001", "57000") are hard-coded in different sources. They should be defined as constants in a single header together.		: Currently most error codes used by pool_send_{error,fatal}_message() etc (e.g. "XX000", "XX001", "57000") are hard-coded in different sources. They should be defined as constants in a single header together.

			=== Create separate process for health checking ===
			: To make main process more stable, it would be better to make separate process which is responsible for health checking.

	== TODOs already done ==		== TODOs already done ==

2013年7月22日 (月) 07:47にIshiiによる

2013-07-22T07:47:45Z

← 古い版		2013年7月22日 (月) 07:47時点における版
58行目:		58行目:
	=== Add SET commnad ===		=== Add SET commnad ===
	: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.		: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.

	~~=== Add testing framework ===~~
	: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.


	=== Put together a definition of error codes into a single header file ===		=== Put together a definition of error codes into a single header file ===
82行目:		78行目:
	=== Allow to load balance even in an explicit transaction in replication mode ===		=== Allow to load balance even in an explicit transaction in replication mode ===
	: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.		: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.

			=== Add testing framework ===
			: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.

2013年7月22日 (月) 07:46にIshiiによる

2013-07-22T07:46:59Z

← 古い版		2013年7月22日 (月) 07:46時点における版
62行目:		62行目:
	: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.		: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.

	~~=== Allow to load balance even in an explicit transaction in replication mode ===~~
	~~: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.~~

	=== Put together a definition of error codes into a single header file ===		=== Put together a definition of error codes into a single header file ===
72行目:		70行目:
	=== Restart watchdog process when it abnormaly exits ===		=== Restart watchdog process when it abnormaly exits ===
	: It would be nice for pgpool main to restart watchdog process when it dies abormaly.		: It would be nice for pgpool main to restart watchdog process when it dies abormaly.
	~~: (Nagata is working on this for pgpool-II 3.3)~~

	=== Synchronize backend nodes information with watchdog when standby pgpool starts up ===		=== Synchronize backend nodes information with watchdog when standby pgpool starts up ===
79行目:		76行目:
	=== Avoid multiple pgpools from executing failover.sh simultaneously. ===		=== Avoid multiple pgpools from executing failover.sh simultaneously. ===
	: In master-slave mode with watchdog, when a backend DB is down, all pgpools execute failover.sh. It might cause something wrong.		: In master-slave mode with watchdog, when a backend DB is down, all pgpools execute failover.sh. It might cause something wrong.
	~~: (Nagata is working on this for pgpool-II 3.3)~~

	=== Add new parameter for searching primary node timeout ===		=== Add new parameter for searching primary node timeout ===
	: pgpool-II uses "recovery_timeout" for searching the primary node timeout after failover. Since this is an abuse of the parameter, we should add new parameter for searching the primary node.		: pgpool-II uses "recovery_timeout" for searching the primary node timeout after failover. Since this is an abuse of the parameter, we should add new parameter for searching the primary node.

			=== Allow to load balance even in an explicit transaction in replication mode ===
			: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.

Admin: /* Pgpool-II TODO list */

2013-07-03T05:59:26Z

Pgpool-II TODO list

← 古い版		2013年7月3日 (水) 05:59時点における版
64行目:		64行目:
	=== Allow to load balance even in an explicit transaction in replication mode ===		=== Allow to load balance even in an explicit transaction in replication mode ===
	: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.		: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.

			=== Put together a definition of error codes into a single header file ===
			: Currently most error codes used by pool_send_{error,fatal}_message() etc (e.g. "XX000", "XX001", "57000") are hard-coded in different sources. They should be defined as constants in a single header together.

	== TODOs already done ==		== TODOs already done ==

Ishii: /* Allow to load balance even in an explicit transaction in replication mode */

2013-06-13T08:00:23Z

Allow to load balance even in an explicit transaction in replication mode

← 古い版		2013年6月13日 (木) 08:00時点における版
63行目:		63行目:

	=== Allow to load balance even in an explicit transaction in replication mode ===		=== Allow to load balance even in an explicit transaction in replication mode ===
	: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be ~~allow~~ in the replication mode as well.		: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.

	== TODOs already done ==		== TODOs already done ==

2013年6月7日 (金) 02:06にIshiiによる

2013-06-07T02:06:22Z

@@ 12行目: / 12行目: @@
 : PS. temporary i have set the weight factor to 0 to the 2-nd and 3-rd postgresql slaves and it behaves ok, because reads and writes only from master.
 === Automatically reattach a node in streaming master/slave configuration ===
 :In streaming master/slave configuration there could be an option to automatically reattach a node if it's up-to-date with the master (0 bytes behind). It often happens that due to minor network outage a slave node is dropped off from pgpool and stays down even if the the node has resumed replication with master and is up-to-date.pgpool already knows how much slave is behind master so i guess this wouldn't be too difficult to implement? (from bugtrack #17)
 === Allow to use client encoding ===
@@ 46行目: / 35行目: @@
 === Support IPV6 network ===
 : This is an obvious requirement.
 === Import PostgreSQL's execption handling ===
@@ 78行目: / 64行目: @@
 === Allow to load balance even in an explicit transaction in replication mode ===
 : Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allow in the replication mode as well.

2013年6月4日 (火) 06:33にIshiiによる

2013-06-04T06:33:38Z

← 古い版		2013年6月4日 (火) 06:33時点における版
75行目:		75行目:
	=== Add testing framework ===		=== Add testing framework ===
	: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.		: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.

			=== Allow to load balance even in an explicit transaction in replication mode ===
			: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allow in the replication mode as well.

2013年5月30日 (木) 12:34にIshiiによる

2013-05-30T12:34:48Z

← 古い版		2013年5月30日 (木) 12:34時点における版
72行目:		72行目:
	=== Add SET commnad ===		=== Add SET commnad ===
	: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.		: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.

			=== Add testing framework ===
			: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.