Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>,
Robert Haas <robertmhaas(at)gmail(dot)com>,
Nikolay Shaplov <dhyan(at)nataraj(dot)su>,
Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist
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.