| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: setLastTid() and currtid() |
| Date: | 2019-04-11 17:27:03 |
| Message-ID: | 21495.1555003623@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2019-03-27 10:01:08 +0900, Inoue, Hiroshi wrote:
>> The above code remains only for PG servers whose version < 8.2.
>> Please remove the code around setLastTid().
> Does anybody else have concerns about removing this interface? Does
> anybody think we should have a deprecation phase? Should we remove this
> in 12 or 13?
I think removing it after feature freeze is not something to do,
but +1 for nuking it as soon as the v13 branch opens. Unless
there's some important reason we need it to be gone in v12?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasia Lubennikova | 2019-04-11 17:29:29 | Re: block-level incremental backup |
| Previous Message | Tom Lane | 2019-04-11 17:20:41 | Re: cache lookup failed for collation 0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-04-11 17:52:08 | Re: setLastTid() and currtid() |
| Previous Message | Andres Freund | 2019-04-11 16:52:14 | Re: setLastTid() and currtid() |