Re: Removal of currtid()/currtid2() and some table AM cleanup

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Hiroshi Saito <hiroshi(at)winpg(dot)jp>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
Subject: Re: Removal of currtid()/currtid2() and some table AM cleanup
Date: 2020-11-25 03:21:57
Message-ID: X73N1ahTsTZE4oia@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 22, 2020 at 08:11:21PM +0900, Michael Paquier wrote:
> Okay, here you go with the attached. If there are any other comments,
> please feel free.

Hearing nothing, applied this one after going through the ODBC driver
code again this morning. Compatibility is exactly the same for
currtid2(), while currtid() is now gone.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2020-11-25 03:28:30 Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Previous Message Bharath Rupireddy 2020-11-25 03:17:52 Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit