| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 18:05:25 |
| Message-ID: | 20190411180525.sqrh7m64r3kudrtk@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Hi,
On 2019-04-11 13:52:08 -0400, Alvaro Herrera wrote:
> As I understand, this setLastTid stuff would cause trouble if used
> with a non-core table AM.
I'm not sure there'd actually be trouble. I mean, what it does for heap
is basically meaningless already, so it's not going to be meaningfully
worse for any other table AM. It's an undocumented odd interface, whose
implementation is also ugly, and that'd be a fair reason on its own to
rip it out though.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-04-11 18:05:41 | Re: Retronym: s/magnetic disk/main data/ |
| Previous Message | Peter Billen | 2019-04-11 18:01:11 | Re: serializable transaction: exclude constraint violation (backed by GIST index) instead of ssi conflict |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-11 18:06:13 | Re: setLastTid() and currtid() |
| Previous Message | Andres Freund | 2019-04-11 17:52:20 | Re: setLastTid() and currtid() |