| 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-21 18:13:35 |
| Message-ID: | 1547394.1605982415@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:
> 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?
Considering that we're preserving this only for backwards compatibility,
I doubt that changing the signature is a good idea. It maybe risks
breaking something, and the ODBC driver is hardly going to notice
any improved ease-of-use.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-11-21 18:33:58 | Re: Removal of currtid()/currtid2() and some table AM cleanup |
| Previous Message | Tom Lane | 2020-11-21 18:07:07 | Re: Connection using ODBC and SSL |