| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Ashwin Agrawal <aagrawal(at)pivotal(dot)io> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Create TOAST table only if AM needs |
| Date: | 2019-05-19 14:03:23 |
| Message-ID: | CAM-w4HNrwi51y_a7EvHVKzKY_6b8Ug9LdUaRY8KEjcRNZuvMzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Just throwing this out there.... Perhaps we should just disable toasting
for non-heap tables entirely for now?
That way at least people can use it and storage plugins just have to be
able to deal with large datums in their own (or throw errors).
On Fri., May 17, 2019, 5:56 p.m. Ashwin Agrawal, <aagrawal(at)pivotal(dot)io>
wrote:
> On Fri, May 17, 2019 at 2:42 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> In any case, it bears saying that
>> tableam is a remarkable accomplishment regardless of whatever
>> shortcomings it has in this area or elsewhere.
>>
>
> Big +1 to this.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-05-19 14:12:28 | Re: Multivariate MCV stats can leak data to unprivileged users |
| Previous Message | Akim Demaille | 2019-05-19 12:47:32 | Remove useless associativity/precedence from parsers |