pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Nikhil Sontakke <nikhil.sontakke@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Nikhil Sontakke <nikhils@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: David Steele <david@pgmasters.net>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Craig Ringer <craig@2ndquadrant.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>
Cc: Sokolov Yura <y.sokolov@postgrespro.ru>
Cc: Stas Kelvich <s.kelvich@postgrespro.ru>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Date: Mon, 23 Jul 2018 21:22:18 +0530
Message-ID: <3B37B16B-A473-4352-ABCF-F23AE314D4F7@2ndquadrant.com> (raw)
In-Reply-To: <20180723141435.ercxxh3bj2uc2mjm@alap3.anarazel.de>
References: <CA+Tgmoa8yDZH0i_58=o6WBESbyqij8m5hKYycV2sWzo2rX9fGg@mail.gmail.com>
	<c9005196-e858-5dfd-80f3-faa076f7102f@2ndquadrant.com>
	<CA+TgmoY2eTJJ5BVgtMkxjwCsrKPbaT_T5g0K5GcmeTk0FeF8DA@mail.gmail.com>
	<20180719194208.j5m7qhdmqp46d6yg@alap3.anarazel.de>
	<20180719223500.lclj45aiojikwnwm@alap3.anarazel.de>
	<CAMGcDxfgg8yP0MsdKRuqwihkrQF=0Mz9Se+0paNGADWaexULjQ@mail.gmail.com>
	<20180720145836.gxwhbftuoyx5h4gc@alap3.anarazel.de>
	<CAMGcDxebtC_ZO6EtLA1MgJ6sWbud3Fjtq9HsBwxxhYfoHJdANw@mail.gmail.com>
	<20180723135009.w25re6qxbb7njrbd@alap3.anarazel.de>
	<CAMGcDxdJNZVq1mX9dZbwEniigi=af8H5dt62C+q2UHwsE+BTaw@mail.gmail.com>
	<20180723141435.ercxxh3bj2uc2mjm@alap3.anarazel.de>

Hi Andres,

>> We can find out if the snapshot is a logical decoding one by virtue of
>> its "satisfies" function pointing to HeapTupleSatisfiesHistoricMVCC.
> 
> I think we even can just do something like a global
> TransactionId check_if_transaction_is_alive = InvalidTransactionId;
> and just set it up during decoding. And then just check it whenever it's
> not set tot InvalidTransactionId.
> 
> 

Ok. I will work on something along these lines and re-submit the set of patches. 

Regards, 
Nikhils



view thread (644+ messages)  latest in thread

Message-ID: <3B37B16B-A473-4352-ABCF-F23AE314D4F7@2ndquadrant.com>
Permalink:  ../3B37B16B-A473-4352-ABCF-F23AE314D4F7@2ndquadrant.com/
Also on:    postgresql.org/message-id/3B37B16B-A473-4352-ABCF-F23AE314D4F7@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nikhil.sontakke@2ndquadrant.com, andres@anarazel.de, nikhils@2ndquadrant.com, robertmhaas@gmail.com, tomas.vondra@2ndquadrant.com, david@pgmasters.net, andrew.dunstan@2ndquadrant.com, simon@2ndquadrant.com, craig@2ndquadrant.com, peter.eisentraut@2ndquadrant.com, petr.jelinek@2ndquadrant.com, y.sokolov@postgrespro.ru, s.kelvich@postgrespro.ru, 9erthalion6@gmail.com, tgl@sss.pgh.pa.us, sawada.mshk@gmail.com
  Subject: Re: [HACKERS] logical decoding of two-phase transactions
  In-Reply-To: <3B37B16B-A473-4352-ABCF-F23AE314D4F7@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox