| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | 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>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist |
| Date: | 2018-01-25 14:40:10 |
| Message-ID: | 6645.1516891210@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Backward compatibility might be an issue, but I doubt that there
are enough people using these options that we couldn't get away
with breaking things, if we're unable to find a decent automatic
conversion method.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-01-25 14:41:38 | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem |
| Previous Message | Alvaro Herrera | 2018-01-25 14:37:26 | Re: reducing isolation tests runtime |