| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: lazy detoasting |
| Date: | 2018-04-10 20:03:11 |
| Message-ID: | CA+Tgmob6D+pGcJ4qZnRaGp5oeR4n+QxaHg1U6Ac6zVgzx9jQUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 10, 2018 at 11:26 AM, Chapman Flack <chap(at)anastigmatix(dot)net> wrote:
> Out of the six GetFooSnapshot()s, would I want to squirrel away
> Active? Oldest? Transaction?
I suspect you want, or maybe need, to use the same snapshot as the
scan that retrieved the tuple containing the toasted datum.
(This advice may be worth what you paid for it.)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-04-10 20:09:33 | Re: submake-errcodes |
| Previous Message | Joshua D. Drake | 2018-04-10 19:51:01 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |