Horton

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

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, "Inoue, Hiroshi" <h-inoue@dream.email.ne.jp>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Hiroshi Saito <hiroshi@winpg.jp>, "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
Date: 2020-11-21T05:45:30Z
Lists: pgsql-hackers

Attachments

On Fri, Nov 20, 2020 at 09:50:08PM -0500, Tom Lane wrote:
> Michael Paquier <michael@paquier.xyz> writes:
>> What about cutting the cake in two and just remove
>> currtid() then?
> 
> +1.  That'd still let us get rid of setLastTid() which is
> the ugliest part of the thing, IMO.

Indeed, this could go.  There is a recursive call for views, but in
order to maintain compatibility with that we can just remove one
function and move the second to use a regclass as argument, like the
attached, while removing setLastTid().  Any thoughts?
--
Michael

Commits

  1. Remove catalog function currtid()