| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch: Write Amplification Reduction Method (WARM) |
| Date: | 2017-04-05 02:21:17 |
| Message-ID: | CABOikdPg3QKXT52wKqCLmd=4EohBBOw_-u6Z6+NW4nxh3f7_Nw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 30, 2017 at 7:55 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> but
> try to access the TOAST table would be fatal; that probably would have
> deadlock hazards among other problems.
Hmm. I think you're right. We could make a copy of the heap tuple, drop the
lock and then access TOAST to handle that. Would that work?
Thanks,
Pavan
--
Pavan Deolasee http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-04-05 02:28:20 | Re: Rewriting the test of pg_upgrade as a TAP test |
| Previous Message | Tsunakawa, Takayuki | 2017-04-05 01:55:47 | Re: Statement timeout behavior in extended queries |