From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Hiroshi Saito <hiroshi(at)winpg(dot)jp>, "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
Subject: | Re: Removal of currtid()/currtid2() and some table AM cleanup |
Date: | 2020-06-04 17:59:05 |
Message-ID: | 20200604175905.mkveizxp3fn7bhyr@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2020-06-03 11:14:48 +0900, Michael Paquier wrote:
> I would like to remove those two functions and the surrounding code
> for v14, leading to some cleanup:
> 6 files changed, 326 deletions(-)
+1
> While on it, I have noticed that heap_get_latest_tid() is still
> located within heapam.c, but we can just move it within
> heapam_handler.c.
What's the point of that change? I think the differentiation between
heapam_handler.c and heapam.c could be clearer, but if anything, I'd
argue that heap_get_latest_tid is sufficiently low-level that it'd
belong in heapam.c.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Rajin Raj | 2020-06-04 18:27:53 | Re: Regarding TZ conversion |
Previous Message | Tom Lane | 2020-06-04 17:57:19 | Re: Atomic operations within spinlocks |