Re: synchronized snapshots

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jim Nasby <jim@nasby.net>, Jeff Davis <pgsql@j-davis.com>, Joachim Wieland <joe@mcknight.de>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-08-24T18:38:42Z
Lists: pgsql-hackers
On lör, 2011-08-20 at 09:56 -0400, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > On tis, 2011-08-16 at 20:35 -0400, Tom Lane wrote:
> > > In fact, now that I think about it, setting the transaction snapshot
> > > from a utility statement would be functionally useful because then you
> > > could take locks beforehand.
> > 
> > Another issue is that in some client interfaces, BEGIN and COMMIT are
> > hidden behind API calls, which cannot easily be changed or equipped with
> > new parameters.  So in order to have this functionality available
> > through those interfaces, we'd need a separately callable command.
> 
> How do they set a transaction to SERIALIZABLE?  Seem the same syntax
> should be used here.

The API typically has parameters to set the isolation level, since
that's a standardized property.