| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: lazy detoasting |
| Date: | 2018-05-03 17:03:05 |
| Message-ID: | 87bmdw8z4x.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Peter" == Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
Peter> The attached test fixes this issue by flattening the toast
Peter> values before storing them into PL/pgSQL variables. It could use
Peter> another check to see if there are other code paths that need
Peter> similar adjustments, but I think it's the right idea in general.
Uhh.
What about:
somevar := (select blah);
or
somevar := function_returning_toasted_val(blah);
or
call someproc(function_returning_toasted_val(blah));
or or or ...
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stas Kelvich | 2018-05-03 17:11:26 | Re: Global snapshots |
| Previous Message | Robert Haas | 2018-05-03 17:01:41 | Re: Built-in connection pooling |