The file is used for parallel queries.
The missing cases are for rewriting GRANT statement. Unfortunately I
have no time to fix it and add nasty pool_log to suppress compiler
warnings.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Ah you're correct, the output from cvs is a lot cleaner. But there's still
There are two problems:
1) pgpool does not handle well multi-statemets. Pgpool saw first SQL
(SET..) and decided that the statement could not be load
balanced. So it sent to all nodes which causeds kind mismatch error
by reason 2).
2) pgpool does not guarantee that OIDs are correctlt
pcp commands do not tell DB nodes are in out-of-sync status. So I'm
not sure what he is expecting here but I think it might be better to
trigger failover in this case (ERROR: pgpool detected difference of
the number of inserted, updated or deleted tuples). Opinions?
--
Tatsuo Ishii
SRA OSS, Inc.
On Sun, Jan 17, 2010 at 10:00 AM, Tatsuo Ishii is...@sraoss.co.jp wrote:
pcp commands do not tell DB nodes are in out-of-sync status. So I'm
not sure what he is expecting here but I think it might be better to
trigger failover in this case (ERROR: pgpool detected difference of
the number of
Hi Devrim,
I installed 2.3.1 and the logging is working again, thanks for fixing
it!
Greetings,
Ger.
On Fri, 2010-01-15 at 14:52 +0100, Ger Apeldoorn wrote:
Hi Devrim,
Thanks, I'll install the update on monday on the test-cluster.
I'll let you know if it solved this issue.
Thanks,
On Mon, 2010-01-18 at 07:55 +0100, Ger Apeldoorn wrote:
I installed 2.3.1 and the logging is working again, thanks for fixing
it!
You are welcome :) Thanks for the feedback.
Regards,
--
Devrim GÜNDÜZ , RHCE
Professional Services, Training, 24x7 Support
Authors: PostgreSQL RPMs, PITRTools,
