| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nikolay Shaplov <dhyan(at)nataraj(dot)su>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist |
| Date: | 2018-01-25 16:29:34 |
| Message-ID: | 12731.1516897774@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Tom Lane wrote:
>> Well, maybe the right answer is to address that. It's clear to me
>> why that would happen if we store these things as reloptions on the
>> toast table, but can't they be stored on the parent table?
> Actually, Nikolay provided a possible solution: if you execute ALTER
> TABLE SET (toast.foobar = xyz), and a toast table doesn't exist, create
> one at that point.
That adds a lot of overhead if you never actually need the toast table.
Still, maybe it's an appropriate amount of effort compared to the size
of the use-case for this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur Zakirov | 2018-01-25 16:51:58 | Re: [PROPOSAL] Shared Ispell dictionaries |
| Previous Message | Peter Eisentraut | 2018-01-25 16:16:27 | Re: Doc tweak for huge_pages? |