| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Rushabh Lathia <rushabh(dot)lathia(at)enterprisedb(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: ERROR: missing chunk number 0 for toast value |
| Date: | 2014-01-07 12:52:51 |
| Message-ID: | 839F3B93-9664-4424-B96D-175E164C3E94@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan7, 2014, at 09:45 , Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> Overall, I'm leaning towards biting the bullet and always detoasting everything in master. Probably best to just leave the stable branches alone.
+1
The fact that de-TOAST-ing can happen lazily is, at least to me, an
implementation detail that shouldn't be observable. If we want to
allow people to use lazy de-TOAST-ing as an optimization tool, we
should provide an explicit way to do so, e.g. by flagging variables
in pl/pgsql as REFERENCE or something like that.
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2014-01-07 13:19:49 | Re: [COMMITTERS] pgsql: Upgrade to Autoconf 2.69 |
| Previous Message | Andres Freund | 2014-01-07 11:54:37 | Re: dynamic shared memory and locks |