| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: [ODBC] getting rid of SnapshotNow |
| Date: | 2013-07-19 15:13:13 |
| Message-ID: | 51E95789.5040506@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
(2013/07/19 22:03), Andres Freund wrote:
> On 2013-07-19 08:57:01 +0900, Inoue, Hiroshi wrote:
>>>> I had the idea they were used for a client-side implementation of WHERE
>>>> CURRENT OF. Perhaps that's dead code and could be removed entirely?
>>>
>>> It's been reported that ODBC still uses them.
>>
>> Though PostgreSQL's TID is similar to Orale's ROWID, it is transient
>> and changed after update operations unfortunately. I implemented
>> the currtid_xx functions to supplement the difference. For example
>>
>> currtid(relname, original tid)
>>
>> (hopefully) returns the current tid of the original row when it is
>> updated.
>
> That is only guaranteed to work though when you're in a transaction old
> enough to prevent removal of the old or intermediate row versions. E.g.
Yes it's what I meant by (hopefully).
At the time when I implemented currtid(), I was able to use TIDs in
combination with OIDs.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-07-19 15:41:14 | Re: Foreign Tables as Partitions |
| Previous Message | Andrew Dunstan | 2013-07-19 15:11:30 | Re: pgindent behavior we could do without |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2013-07-19 15:49:11 | Re: getting rid of SnapshotNow |
| Previous Message | Hiroshi Inoue | 2013-07-19 13:46:40 | Re: Windows UNICODE driver vs ANSI Driver |