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 1i0iFG-0001D8-TO for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Aug 2019 08:14:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i0iFF-0004cT-MD for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Aug 2019 08:14:57 +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 1i0iFF-0004Vw-9N for pgsql-bugs@lists.postgresql.org; Thu, 22 Aug 2019 08:14:57 +0000 Received: from mail-pf1-x441.google.com ([2607:f8b0:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i0iFD-0004bE-0K for pgsql-bugs@lists.postgresql.org; Thu, 22 Aug 2019 08:14:56 +0000 Received: by mail-pf1-x441.google.com with SMTP id o70so3424674pfg.5 for ; Thu, 22 Aug 2019 01:14:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:message-id:to:cc:subject:from:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=Jhpjrt6Po298jZZhRP7uwp0QSB1MCD0JRzx2O4HSGng=; b=YDd1KAcAjVj9DqQbKfX24O9gz6HmNgZSNNBSOKr84VCJNIa9A7fUikEin7FIgPaYir zoXE7Uyy3zUS5vr22sraf0e9lTWZua/E71H2ccqJgzEQA7aF5y7SewNNA01Hfuq8h4ut OH5at0i8+9qGMb/2bPFlzDYGMJCvfZSVBoBt/mptByjTzYXgVhgRvDg9pXqiMpjuJ6+a GV4ycFMfkuvcLUY3VNe9x16v7Jl795vUvR+XoOwP5d5UzfEIV7FmUbRkCM1iabjIgfSc u4MtsL0bPcnF8C2o4aueaaEsDQ+8qJcVvZRwnzbcHlIRKx/OqRLBRZ+ryZrHm1Y+oaMX Iygw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:to:cc:subject:from:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=Jhpjrt6Po298jZZhRP7uwp0QSB1MCD0JRzx2O4HSGng=; b=DIyzo/ETAbdnHlLRa45liyetzKZoLEbGXsLPgD/zSYmSWZwfjUbqJ1TUVNMuPQ7DGQ b61x4S2yB7d8qcTdg3DAxQt7kQp2lsn+VjKJtNx+fs0dNJmor71xDThEKe1ltsd4NN4w 9Lbldkf3t+SQychi3wPkUu0k/ziuBUGdxJvFtUrj4jSVciQKMN2Dm3O7ZQ9uHIdf+xak as0Fb0DD+klLaNdjVXD21wNqnGExcTVL8I0dMsyG5nZexzaX4PmZrtY0xJI7wt6WcWlH c7yDq/Xfj9Ao94s+dtedbbg2LTkKr6QluNN/nOH2PBPNgCHU/O8DIrkfwnrsN9EGpNXK Bzyw== X-Gm-Message-State: APjAAAXCMnrrJZykMKDISKRGSxg1G76Q9OveaUxU+eXkc/bxZFqTTQBK FTNPXudKFXGoCxp8q38MnFo= X-Google-Smtp-Source: APXvYqxIguZhn0jzmBafCYw8jaamaDMilPOZ+kPfkumGPyjxF/bJWtQAkdJjMLwMLBKilJwJe+p1Ow== X-Received: by 2002:a17:90a:feb:: with SMTP id 98mr3923730pjz.55.1566461692757; Thu, 22 Aug 2019 01:14:52 -0700 (PDT) Received: from localhost (w204177.dynamic.ppp.asahi-net.or.jp. [121.1.204.177]) by smtp.gmail.com with ESMTPSA id a189sm34120079pfa.60.2019.08.22.01.14.49 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 22 Aug 2019 01:14:52 -0700 (PDT) Date: Thu, 22 Aug 2019 17:14:39 +0900 (Tokyo Standard Time) Message-Id: <20190822.171439.14634665.horikyota.ntt@gmail.com> To: michael@paquier.xyz Cc: keith.fiske@crunchydata.com, ejberdecia@yahoo.com, david.rowley@2ndquadrant.com, amitlangote09@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15954: Unable to alter partitioned table to set logged From: Kyotaro Horiguchi In-Reply-To: <20190821134434.GA9383@paquier.xyz> References: <1703025078.5205270.1565786782053@mail.yahoo.com> <20190821134434.GA9383@paquier.xyz> User-Agent: Mew version 6.5 on Emacs 22.2 / Mule 5.0 =?iso-2022-jp?B?KBskQjpnGyhCKQ==?= / Meadow-3.01-dev (TSUBO-SUMIRE) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk At Wed, 21 Aug 2019 22:44:34 +0900, Michael Paquier wrote in <20190821134434.GA9383@paquier.xyz> > On Wed, Aug 21, 2019 at 09:24:38AM -0400, Keith Fiske wrote: > > As the others have stated, I think we just need to get some sort of > > consistent method of handling this. Currently running an ALTER TABLE on the > > parent to change the UNLOGGED state simply does nothing which is not > > intuitive whatsoever. Even if it's just throwing an error saying you cannot > > change this property, that would be better until a more thorough solution > > can be implemented in the future. > > One problem with an error is that it may break existing application > code :( It is quite strange that we can CREATE both LOGGED and UNLOGGED partitioned table but cannot ALTER the property. I believe no one does ALTER TABLE SET (UN)LOGGED expecting it is silently ignored. But I'm not sure about the CREATE case.. CREATE UNLOGGED VIEW is complained as "cannot be unlogged bacause they do not have storage" but I don't think partitioned tables don't necessarily need to behave so. Even if any, I'm not sure what those who does "CREATE UNLOGGED TABLE parent" expect (*), I think we can ignore and always make the new table as LOGGED. The only trouble case is happen only for those who checks the property. *: Maybe they expect that the property propagates to children, but anyway we are not doing so. regards. -- Kyotaro Horiguchi NTT Open Source Software Center