Tatsuo,
Thank you for your reply. Apologies for missing this out.
The reset_query_list is set to 'ABORT; RESET ALL; SET SESSION
AUTHORIZATION DEFAULT'.
Also something noticed was when we do a prepare it is put in a
transaction (BEGIN;. COMMIT) an is fired on both the server.
Regards,
Thanks for the report. I will look into this.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Hi,
I'm wondering why this is caused when I run the following as a quick
test.
can this syntax error cause any DB mismatch and make the DB get out of
sync cause on a real scenario, one time a few minutes
Hi Ukasz
I had the same issue while recovering the second node. (This happened only
when there were some parallel database activities going)
Node 1 Node 2
Test 1 -
a) Node 2 is down,
b) I was executing an update statement on a 4 rows of data using pgpool
(which is only updating node 1) (in