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 20180410130644.boudfha2hcoaseiw@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist  (Nikolay Shaplov <dhyan@nataraj.su>)
List pgsql-hackers
Nikolay Shaplov wrote:
> В письме от 25 января 2018 11:29:34 пользователь Tom Lane написал:
> > Alvaro Herrera <alvherre@alvh.no-ip.org> writes:

> > > 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.
>
> I think this overhead case is not that terrible if it is properly warned ;-)

Let's go with this idea, which seems to me better than the statu quo.
There are a couple of other proposals, but they seem to require a lot of
work in exchange for unclear benefits.

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


pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOASTtable does not exist
Next
From: David Steele
Date:
Subject: Re: Function to track shmem reinit time