Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gzU8M-0007Rd-S6 for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Feb 2019 22:26:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gzU8L-0002NV-JD for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Feb 2019 22:26:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gzU8L-0002NO-91 for pgsql-hackers@lists.postgresql.org; Thu, 28 Feb 2019 22:26:29 +0000 Received: from mail-qk1-x744.google.com ([2607:f8b0:4864:20::744]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gzU83-0000OM-So for pgsql-hackers@lists.postgresql.org; Thu, 28 Feb 2019 22:26:28 +0000 Received: by mail-qk1-x744.google.com with SMTP id r21so13103161qkl.11 for ; Thu, 28 Feb 2019 14:26:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=pitFxUDvjKKORfiEzkNx3mT0KBoM8pzVNxtLF1WSD34=; b=N/tpoZeOuyLdyp5Swx6o2S8kDaMzdz5oM+FnAPdQyL46C7PcVJdfnKMaKBVKG1nxRQ 5LKgAbuUQm008QIjY/uYhQK3OH82bHEjnTJOeQOrh0pKwS1xWSfhnbfRTo8lhzhFz0Dj Q0/wchC29XhrIdHw0kAGK1PIYNpC+7iV/wjyPwwM5QY99gX2kmDJ/0xn2HxWhQAI54oy e6c450lvnHLgg6UH1G1gTzBMveCx9L2WvUe4nRzH+qoRTf5PkiU0ekLnDnXBaEfleWYK usBrCemUtMwN+eUXNlJL0te9ZrlcgDiepEoUxEEwhOZbi205P46zhk5zDFybIpOzU1Ne l3wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=pitFxUDvjKKORfiEzkNx3mT0KBoM8pzVNxtLF1WSD34=; b=eGI8Po/Mn+SEghtG/aE2TjJwtTqKUAxx+b3kuV+I2WiMwnFHCGhPPJ/RAcGUPFvJhQ K+kC5btnHd+kdVy5SCL9a4vOL3vLBMKcGCmxECFa+ope55qWL2+TiMHsgtzvN56eFU97 A7Y+aZJb/rbGN1gPOFGGnNUlRhFLFQmdUaRLiL3SsFFB1y/mOcgrP79kpJPOCe4Zr96Q /qT8MtX7uJWqsTYnXt3LqEmv7QnmJpyHGFoMlmxZMKMKop8Z8HHdHZ2wYyjelJhDsBOf RLBeP4YCyUjpDlb3RTuGBV/Xoc5JItDzAOljy0hTE13tEW+LmygDMECcLmvaTyFaaGdY 7ASQ== X-Gm-Message-State: APjAAAUHo8JkSgy87iS2uxvO6++HRqAGSdMQ95BEYBbzHfB1XG6xOtq3 QLk0UCGgT6+RYAgnuTdiZzXf3A== X-Google-Smtp-Source: APXvYqxGRpokdIkWwEuOtZCs4VAuKK+39umiyKWnepyxnvDOHaDk6Qv1xxoPBcc6ssyDJmH/oloF8A== X-Received: by 2002:a05:620a:13ad:: with SMTP id m13mr1504461qki.59.1551392770262; Thu, 28 Feb 2019 14:26:10 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([191.126.227.205]) by smtp.gmail.com with ESMTPSA id c2sm19371193qtc.41.2019.02.28.14.26.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 28 Feb 2019 14:26:09 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id C68F6121419; Thu, 28 Feb 2019 19:25:56 -0300 (-03) Date: Thu, 28 Feb 2019 19:25:56 -0300 From: Alvaro Herrera To: Robert Haas Cc: Pg Hackers Subject: Re: propagating replica identity to partitions Message-ID: <20190228222556.GA23981@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Feb-20, Robert Haas wrote: > On Wed, Feb 20, 2019 at 12:38 PM Alvaro Herrera > wrote: > > Maybe the ALL IN TABLESPACE and OWNED BY sub-forms should be split to a > > separate para. I suggest: > > > > : This form changes the table's tablespace to the specified tablespace > > : and moves the data file(s) associated with the table to the new > > : tablespace. Indexes on the table, if any, are not moved; but they > > : can be moved separately with additional SET TABLESPACE commands. > > : When applied to a partitioned table, nothing is moved, but any > > : partitions created afterwards with CREATE TABLE PARTITION OF > > : will use that tablespace. > > : > > : All > > : tables in the current database in a tablespace can be moved by using > > : the ALL IN TABLESPACE form, which will lock all tables to be moved > > : first and then move each one. This form also supports OWNED BY, > > : which will only move tables owned by the roles specified. If the > > : NOWAIT option is specified then the command will fail if it is > > : unable to acquire all of the locks required immediately. Note that > > : system catalogs are not moved by this command, use ALTER DATABASE or > > : explicit ALTER TABLE invocations instead if desired. The > > : information_schema relations are not considered part of the system > > : catalogs and will be moved. See also CREATE TABLESPACE. > > Seems reasonable. Pushed this bit, thanks. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services