Re: chained transactions - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: chained transactions
Date
Msg-id alpine.DEB.2.21.1811041203540.7070@lancre
Whole thread Raw
In response to Re: chained transactions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: chained transactions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hello Peter,

> Attached is a rebased patch set.  No functionality changes.

Patch applies cleanly, compile, global make check ok, doc gen ok.

Shouldn't psql tab completion be updated as well?

About the code:

I must admit that do not like much the three global variables & 
Save/Restore functions. I'd suggest saving directly into 3 local variables 
in function CommitTransactionCommand, and restoring them when needed. Code 
should not be longer. I'd would not bother to skip saving when not 
chaining.

Copying & comparing nodes are updated. Should making, outing and reading 
nodes also be updated?

About the tests: I'd suggest to use more options on the different tests, 
eg SERIALIZABLE, READ ONLY… Also ISTM that tests should show 
transaction_read_only value as well.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: pg_dump multi VALUES INSERT
Next
From: Dmitry Dolgov
Date:
Subject: Re: [HACKERS] Lazy hash table for XidInMVCCSnapshot (helps Zipfian a bit)