Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YVx7c-0004X7-4t for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Mar 2015 07:01:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YVx7b-0002Im-JP for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Mar 2015 07:01:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YVx7a-0002If-65 for pgsql-hackers@postgresql.org; Thu, 12 Mar 2015 07:01:30 +0000 Received: from mail-wg0-x22b.google.com ([2a00:1450:400c:c00::22b]) by makus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YVx7W-0002S5-Mk for pgsql-hackers@postgresql.org; Thu, 12 Mar 2015 07:01:28 +0000 Received: by wggy19 with SMTP id y19so14215066wgg.2 for ; Thu, 12 Mar 2015 00:01:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=cGhletTvSmIE80pjUPyjqw+dy10xW79wscWQq6hXGzQ=; b=gjReXEoXMYnEX0VOaavmqdD6e1jQpEsOqoHUP7ZPEGaNTnOYjImrxuJc/DhoqgdNXj aAYtUU0+DQ4cIHce3DnZkViKYyGZbrQ9fBWe8YklxOI5rfzbcXaxQUma4CAUxpcGXZnh APOfHQ+KKKkKmVe5YX+OVOOjnHtPydUICUig+Sy3wyT1FJiePPdERWoHRH2D2J0RSsyN ziT0umRDbC04PSD2WRrK2zEa2gcwtgBQg2iOvcFn3iyNyInhpO7LZA9E7FJlAPdK4J8s PI76jYqsJm8D+fWWVF4xhkbsDshAcZ8uBPldPKXclSWuuxyr1kQXgRGdkythRt9I/35d 5RSA== X-Received: by 10.194.6.70 with SMTP id y6mr82317435wjy.97.1426143685138; Thu, 12 Mar 2015 00:01:25 -0700 (PDT) Received: from [192.168.1.20] (alo33-3-78-225-150-42.fbx.proxad.net. [78.225.150.42]) by mx.google.com with ESMTPSA id gz3sm9332124wib.1.2015.03.12.00.01.24 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Mar 2015 00:01:24 -0700 (PDT) Message-ID: <550139C3.2040704@gmail.com> Date: Thu, 12 Mar 2015 08:01:23 +0100 From: Julien Tachoires User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Alvaro Herrera , Robert Haas CC: Andreas Karlsson , Alex Shulgin , Jaime Casanova , Pg Hackers Subject: Re: patch : Allow toast tables to be moved to a different tablespace References: <1323956011-sup-9589@alvh.no-ip.org> <87r3wn5lhq.fsf@commandprompt.com> <54A2127D.5020907@proxel.se> <54F5CFDE.20301@gmail.com> <54FE2C23.1080604@proxel.se> <20150310122740.GZ3291@alvh.no-ip.org> In-Reply-To: <20150310122740.GZ3291@alvh.no-ip.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 10/03/2015 13:27, Alvaro Herrera wrote: > Robert Haas wrote: >> On Mon, Mar 9, 2015 at 7:26 PM, Andreas Karlsson 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers