| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Subject: | Re: extensible external toast tuple support |
| Date: | 2013-07-02 17:40:02 |
| Message-ID: | CA+TgmoYqBp4hOuOgj+hh5qB4huKxgjZwfVqAeOGb+v_sW1AO3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 2, 2013 at 11:06 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> In that case the old value will rather likely just have been read just
> before, so the price of rereading should be relatively low.
Maybe in terms of I/O, but there's still CPU.
> is a rather valid point. I've split the patch accordingly. The second
> patch is *not* supposed to be applied together with patch 1 but rather
> included for reference.
OK, committed patch 1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2013-07-02 17:43:31 | Re: New regression test time |
| Previous Message | Andres Freund | 2013-07-02 17:34:43 | Re: Eliminating PD_ALL_VISIBLE, take 2 |