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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-22 02:39:28
Message-ID: 1767456.1606012768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> So, what you are basically saying is to switch currtid_byreloid() to
> become a function local to tid.c. And then have just
> currtid_byrelname() and currtid_for_view() call that, right?

Yeah, that sounds about right.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2020-11-22 03:06:25 Printing backtrace of postgres processes
Previous Message Andy Fan 2020-11-22 02:35:30 Re: Different results between PostgreSQL and Oracle for "for update" statement