Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist
Date
Msg-id 12731.1516897774@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOASTtable does not exist  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Doc tweak for huge_pages?
Next
From: Arthur Zakirov
Date:
Subject: Re: [PROPOSAL] Shared Ispell dictionaries