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-22 11:11:21
Message-ID: 20201122111121.GA23947@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 21, 2020 at 09:39:28PM -0500, Tom Lane wrote:
> 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.

Okay, here you go with the attached. If there are any other comments,
please feel free.
--
Michael

Attachment Content-Type Size
currtid-remove-v4.patch text/x-diff 13.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Phil Florent 2020-11-22 12:50:55 Parallel plans and "union all" subquery
Previous Message Gilles Darold 2020-11-22 10:05:52 Re: Issue with server side statement-level rollback