> Ah, sorry, that's me snipping the log too much, then. :-( > - We do have set insert_lock=true from the very beginning. > - We do *not* send any /*NO INSERT LOCK*/ comments. > Hence, LOCKs do show up in the log.
Oh, ok. > The queries come from two different clients, hence we end up with two > different postgresql threads trying to use the table. > I extracted both relevant threads from both postgres logs below > (irrelevant internals anonymized, other threads removed): [snip] > Interestingly enough, only the thread using nextval is locking - > but, afaict, too late in the second case? > > The order of events on node 0 is that of pgpool's own log, > so it seems to me that insert_lock=true isn't quite working as expected? Maybe. I'll look into this. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
