| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Global snapshots |
| Date: | 2018-05-03 15:28:52 |
| Message-ID: | CAD21AoBph=12dbyH6KJJ--UkBKtzugT3iJb8CPL5fY7tdpLW8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 2, 2018 at 1:27 AM, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> wrote:
> 1) To achieve commit atomicity of different nodes intermediate step is
> introduced: at first running transaction is marked as InDoubt on all nodes,
> and only after that each node commit it and stamps with a given GlobalCSN.
> All readers who ran into tuples of an InDoubt transaction should wait until
> it ends and recheck visibility.
I'm concerned that long-running transaction could keep other
transactions waiting and then the system gets stuck. Can this happen?
and is there any workaround?
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-03 15:38:10 | Re: Optimize Arm64 crc32c implementation in Postgresql |
| Previous Message | Liudmila Mantrova | 2018-05-03 14:57:27 | Re: documentation is now XML |