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

From Kevin Grittner
Subject Re: pgsql_fdw, FDW for PostgreSQL server
Date
Msg-id 4F420ADE0200002500045893@gw.wicourts.gov
Whole thread Raw
In response to Re: pgsql_fdw, FDW for PostgreSQL server  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: pgsql_fdw, FDW for PostgreSQL server  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
List pgsql-hackers
"Albe Laurenz" <laurenz.albe@wien.gv.at> wrote:
> If your query involves foreign scans on two foreign tables on the
> same foreign server, these should always see the same snapshot,
> because that's how it works with two scans in one query on local
> tables.
That makes sense.
> So I think it should be REPEATABLE READ in all cases -
> SERIALIZABLE is not necessary as long as all you do is read.
That depends on whether you only want to see states of the database
which are consistent with later states of the database and any
invariants enforced by triggers or other software.  See this example
of how a read-only transaction can see a bogus state at REPEATABLE
READ or less strict transaction isolation:
http://wiki.postgresql.org/wiki/SSI#Read_Only_Transactions
Perhaps if the transaction using the pgsql_fdw is running at the
SERIALIZABLE transaction isolation level, it should run the queries
at the that level, otherwise at REPEATABLE READ.
-Kevin


pgsql-hackers by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: [v9.2] Add GUC sepgsql.client_label
Next
From: Tom Lane
Date:
Subject: Re: Incorrect behaviour when using a GiST index on points