| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: getting rid of SnapshotNow |
| Date: | 2013-07-19 15:49:11 |
| Message-ID: | 51E95FF7.4000004@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
(2013/07/18 21:46), Robert Haas wrote:
> There seems to be a consensus that we should try to get rid of
> SnapshotNow entirely now that we have MVCC catalog scans, so I'm
> attaching two patches that together come close to achieving that goal:
...
> With that done, the only remaining uses of SnapshotNow in our code
> base will be in currtid_byreloid() and currtid_byrelname(). So far no
> one on this list has been able to understand clearly what the purpose
> of those functions is, so I'm copying this email to pgsql-odbc in case
> someone there can provide more insight. If I were a betting man, I'd
> bet that they are used in contexts where the difference between
> SnapshotNow and SnapshotSelf wouldn't matter there, either.
Using SnapshotSelf instead of SnapshotNow for currtid_ () wouldn't
matter.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2013-07-19 15:59:01 | Re: Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions) |
| Previous Message | Robert Haas | 2013-07-19 15:41:14 | Re: Foreign Tables as Partitions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-07-19 16:02:30 | Re: [HACKERS] getting rid of SnapshotNow |
| Previous Message | Hiroshi Inoue | 2013-07-19 15:13:13 | Re: [ODBC] getting rid of SnapshotNow |