| 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-21 05:45:30 |
| Message-ID: | 20201121054457.GE6052@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 20, 2020 at 09:50:08PM -0500, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| currtid-remove-v3.patch | text/x-diff | 10.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-11-21 07:29:19 | Re: [doc] improve tableoid description |
| Previous Message | Tom Lane | 2020-11-21 02:50:08 | Re: Removal of currtid()/currtid2() and some table AM cleanup |