| From: | Julien Tachoires <julmon(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, Alex Shulgin <ash(at)commandprompt(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch : Allow toast tables to be moved to a different tablespace |
| Date: | 2015-03-12 07:01:23 |
| Message-ID: | 550139C3.2040704@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/03/2015 13:27, Alvaro Herrera wrote:
> Robert Haas wrote:
>> On Mon, Mar 9, 2015 at 7:26 PM, Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
>
>>> I think we should allow moving the indexes for consistency. With this patch
>>> we can move everything except for TOAST indexes.
>>
>> It might make sense to always put the TOAST index with the TOAST
>> table, but it seems strange to put the TOAST index with the heap and
>> the TOAST table someplace else. Or at least, that's how it seems to
>> me.
>
> Agreed. It doesn't seem necessary to allow moving the toast index to a
> tablespace other than the one containing the toast table. In other
> words, if you move the toast table, the index always follows it, and
> there's no option to move it independently.
This behaviour is already implemented, the TOAST index always follows
the TOAST table. I'll add a couple of regression tests about it.
--
Julien
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rikard Pavelic | 2015-03-12 08:07:43 | timestamp format escape rules |
| Previous Message | Pavel Stehule | 2015-03-12 06:54:49 | Re: proposal: searching in array function - array_position |