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

From Alvaro Herrera
Subject Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOASTtable does not exist
Date
Msg-id 20180125155519.gmafmdoh76nriazf@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist
List pgsql-hackers
Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> > On 1/23/18 13:39, Robert Haas wrote:
> >> I don't understand.  AAUI, it is currently the case that if you set
> >> the options before the TOAST table exists, they are lost.
> 
> > Well, that's also weird.
> 
> 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.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: JIT compiling with LLVM v9.0
Next
From: "David G. Johnston"
Date:
Subject: CONSTANT/NOT NULL/initializer properties for plpgsql record variables