Is it really difficult for postgres_fdw to implement READ COMMITTED isolation?

From: Jinhua Luo <luajit(dot)io(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Is it really difficult for postgres_fdw to implement READ COMMITTED isolation?
Date: 2018-09-18 14:58:20
Message-ID: CAAc9rOzKSOVvc3hqXNH7v-2EjXaE4NrdqybKxEz3Yi4j7Q+PHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

https://www.postgresql.org/docs/current/static/postgres-fdw.html#id-1.11.7.43.12

As the doc said, the REPEATABLE READ isolation level is used to get
snapshot-consistent results.

But is it possible that postgres_fdw could get to know which remote
queries involved by each top outer command in the local transaction,
and use the same snapshot in the remote server to execute them
sequentially? For example, could we use PREPARE TRANSACTION and SET
TRANSACTION SNAPSHOT to archive this goal? Then we could use READ
COMMITTED on both sides?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2018-09-18 15:28:53 Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
Previous Message Tom Lane 2018-09-18 14:45:09 Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi