[Pgpool-general] pgpool detected difference of the number of inserted, updated or deleted tuples.

[Andre Felipe Machado]

Hello,
Yes, tried that, but did not solve it. Only the cited approach did it.
We even tried the same idea: explicitly locking the entire table during inserts,
updates, deletes. The results were as expected at performance (VERY poor as
pgpool "serialized" all these previously simultaneus transactions), and an
unexpected side effect (with our confs): RAM usage "exploded" during stress test
and we had to hard reboot the machine.
The kind of transaction row locking was the less penalty we found.

We are still stress loading the pool and it did not have a single failure since
then.
It worked for our php app, but it should be tested for other apps. 
How about binary only unmodifiable apps?
Regards.
Andre Felipe Machado
http://www.techforce.com.br




Tatsuo Ishii <ishii at sraoss.co.jp> wrote ..
> Have you tried "insert_lock" directive in pgpool.conf?
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp