Olivier MATROT wrote: > Serialization conflict detection is done in src/backend/storage/lmgr/predicate.c, where transactions > that are doomed to fail are marked as such with the SXACT_FLAG_DOOMED flag. > > I simply added elog(NOTIFY,...) calls with the DEBUG1 level, each time the flag is set, compiled the > code and give it a try. > > The results are amazing for me, because this simple modification allows me to see which query is > marking other running transactions to fail. > > Without this information, this is really difficult to understand what’s going on and, eventualy, > modify my program to make my transactions run successfully more often. > > What is the correct way to suggest this improvement for a future version of PostgreSQL ? First you should make this suggestion on the -hackers list; if you have a patch against HEAD, attach it. If you get positive or encouraging feedback, add the patch to the next commitfest. People who contribute code are also expected to review code. Read the Developer FAQ: https://wiki.postgresql.org/wiki/Developer_FAQ Another helpful article: https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
