Re: pgsql_fdw, FDW for PostgreSQL server - Mailing list pgsql-hackers

From Shigeru Hanada
Subject Re: pgsql_fdw, FDW for PostgreSQL server
Date
Msg-id CAEZqfEcvmUHSY5jGGrQ+bym+wjgHYX26z6572hhB0eCf=uq56g@mail.gmail.com
Whole thread Raw
In response to Re: pgsql_fdw, FDW for PostgreSQL server  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: pgsql_fdw, FDW for PostgreSQL server
List pgsql-hackers
<p><br /> 2012/02/21 0:58 "Kevin Grittner" <<a
href="mailto:Kevin.Grittner@wicourts.gov">Kevin.Grittner@wicourts.gov</a>>:<br/> ><br /> > "Albe Laurenz"
<<ahref="mailto:laurenz.albe@wien.gv.at">laurenz.albe@wien.gv.at</a>> wrote:<br /> ><br /> > > I read
theexample carefully, and it seems to me that it is<br /> > > necessary for the read-only transaction (T3)v to be
SERIALIZABLEso<br /> > > that T1 is aborted and the state that T3 saw remains valid.<br /> ><br /> >
Correct.<br/> Hm, agreed that isolation levels < REPEATABLE READ are not sufficient for pgsql_fdw's usage.  I'll
examinethe example and fix pgsql_fdw.<p>Thanks. 

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: 16-bit page checksums for 9.2
Next
From: Bruce Momjian
Date:
Subject: Re: 16-bit page checksums for 9.2