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 1h7NP1-0008AN-JQ for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Mar 2019 16:52:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h7NOz-0003kQ-Gq for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Mar 2019 16:52:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h7NOz-0003kJ-2A for pgsql-hackers@lists.postgresql.org; Fri, 22 Mar 2019 16:52:17 +0000 Received: from mail-qt1-x842.google.com ([2607:f8b0:4864:20::842]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h7NOw-0002Dj-0h for pgsql-hackers@lists.postgresql.org; Fri, 22 Mar 2019 16:52:15 +0000 Received: by mail-qt1-x842.google.com with SMTP id v32so3222204qtc.10 for ; Fri, 22 Mar 2019 09:52:13 -0700 (PDT) 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=LVwqx8Cr4ziliyotUA6i9WxLpaIECxlWrkkQItl5GE8=; b=i9pfQjsTkT7dhCMvAEoiyvIYJIt0GHPJB1ZXaAy6cVYO9y1IwsqLTYW5nbIJAwns9T 297d4DwK7+CH3uxAKLIX+u1Z0scqsmBdM8MT0NxjsQRVWjF5Uf/RjZIrWWUt7mqqSXb9 YTlSqmBTUVhtIyiKZBEVNWvjm37pPVj/TyFGsPqpfFhLRB7BGlIaUmqyCfY2K0LQK28p 28qdSrqLXkv0fANUzWpnHbR4Snwtr8KijTy88tkppY4PIOFDFh/0MCnCVdZ15/Rc1j4E KvLUmLPZaloA/heFfLMpwrdcuyzfh5dVVbFO0Q9CN6+TWYNJ0wpgzy5mSRYRFP8SF21e 0qBw== 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=LVwqx8Cr4ziliyotUA6i9WxLpaIECxlWrkkQItl5GE8=; b=V/KIsi0Ts96+LUzNZdcVUhyrIj0izmV3P7WjxDkhzi7Vt8lt8RKOBC1awKhWlT1AJr 4hiNtVtaG3cRLhrAmw+9mWfs3WlFk4lhUvfR09LBIEtFpm7Ml2Te2wFC5OZOBc9AmPL7 y7680+FTz5M4v/uiK9LqSE5UPIibdISzdTEaMcPCZJ4oHStlykfwBTDvJU6xHS1r4Uhy najZyN4rs1i+56sA9vh1/+Ri2zYjV80kphto2Rdzn1OfYPkvN9461NvRRuuEPN1shzPD IM7sZ+/DGrVkJaTmKaKpzP8wttoE7iY88EXESYGFAn4dI17WplAdehhyzCQfI/yMQbdr +5fw== X-Gm-Message-State: APjAAAVvZPpbx/3LmRW1ZE7lbH7vRqNA3RU/gSABO9onPGAs5RuJ2qJH qJUCD0UMuUhkmwVFI7SoXBHkrA== X-Google-Smtp-Source: APXvYqw7AntiElkDCW+MOet6wUu7K43fE70KxUWQ7/LMJ2WE3s0hCky/sSv2N9+qgwmJNOp274LrIA== X-Received: by 2002:ac8:3585:: with SMTP id k5mr8881400qtb.55.1553273533018; Fri, 22 Mar 2019 09:52:13 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id 92sm5174185qtc.97.2019.03.22.09.52.12 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 22 Mar 2019 09:52:12 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 7BB2A1207D8; Fri, 22 Mar 2019 13:52:09 -0300 (-03) Date: Fri, 22 Mar 2019 13:52:09 -0300 From: Alvaro Herrera To: Robert Haas Cc: Peter Eisentraut , Pg Hackers Subject: Re: propagating replica identity to partitions Message-ID: <20190322165209.GA15613@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-Mar-22, Robert Haas wrote: > On Thu, Mar 21, 2019 at 5:01 PM Alvaro Herrera wrote: > > I already argued that TABLESPACE and OWNER TO are documented to work > > that way, and have been for a long time, whereas REPLICA IDENTITY has > > never been. If you want to change long-standing behavior, be my guest, > > but that's not my patch. On the other hand, there's no consensus that > > those should be changed, whereas there no opposition specifically > > against changing this one, and in fact it was reported as a bug to me by > > actual users. > > Well, you have a commit bit, and I cannot prevent you from using it, > and nobody else is backing me up here, but it doesn't change my > opinion. Can I ask for more opinions here? Should I apply this behavior change to pg12 or not? If there's no consensus that it should be changed, I wouldn't change it. To recap: my proposed change is to make ALTER TABLE ... REPLICA IDENTITY when applied on a partitioned table affect all of its partitions instead of expecting the user to invoke the command for each partition. At the same time, I am proposing not to change to have recursive behavior other forms of ALTER TABLE in one commit, such as TABLESPACE and OWNER TO, which currently do not have recursive behavior. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services