| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 15:55:19 |
| Message-ID: | 20180125155519.gmafmdoh76nriazf@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-01-25 16:00:37 | CONSTANT/NOT NULL/initializer properties for plpgsql record variables |
| Previous Message | Konstantin Knizhnik | 2018-01-25 15:40:53 | Re: JIT compiling with LLVM v9.0 |