| From: | Nikolay Shaplov <dhyan(at)nataraj(dot)su> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist |
| Date: | 2018-01-23 18:53:24 |
| Message-ID: | 4583775.H7fJV3jYc8@x200m |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
В письме от 23 января 2018 12:03:50 пользователь Peter Eisentraut написал:
> >>> This patch raises error if user tries o set or change toast.* option for
> >>> a table that does not have a TOST relation.
> >
> > There might be a case for raising a warning in this situation,
> > but I would disagree with making it a hard error in any case.
> > All that's going to accomplish is to break people's scripts and
> > get them mad at you.
>
> It might also be useful to set these reloptions before you add a new
> column to a table.
As Robert have just said, this will not work with current master.
If we, as I've suggested in previous letter, will force TOAST creation if
toast.* option is set, then your use case will also work.
--
Do code for fun.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-01-23 19:06:07 | Re: using index or check in ALTER TABLE SET NOT NULL |
| Previous Message | Peter Geoghegan | 2018-01-23 18:50:59 | Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation) |