Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlbCC-0006de-DL for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jun 2020 16:45:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jlbCB-0001NI-8w for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jun 2020 16:45:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlbCA-0001L8-Vt for pgsql-hackers@lists.postgresql.org; Wed, 17 Jun 2020 16:45:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlbC7-0004ZL-Iz for pgsql-hackers@postgresql.org; Wed, 17 Jun 2020 16:45:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 05HGjjiT1449609; Wed, 17 Jun 2020 12:45:46 -0400 From: Tom Lane To: Robert Haas cc: Amit Kapila , amul sul , PostgreSQL-development Subject: Re: [Patch] ALTER SYSTEM READ ONLY In-reply-to: References: <1445158.1592405895@sss.pgh.pa.us> <1448927.1592411268@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 17 Jun 2020 12:34:53 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1449607.1592412345.1@sss.pgh.pa.us> Date: Wed, 17 Jun 2020 12:45:45 -0400 Message-ID: <1449608.1592412345@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > On Wed, Jun 17, 2020 at 12:27 PM Tom Lane wrote: >> Which of the things I mentioned don't require writing WAL? > Writing hint bits and marking index tuples as killed do not write WAL > unless checksums are enabled. And your point is? I thought enabling checksums was considered good practice these days. >> You're right that these are the same things that we already forbid on a >> standby, for the same reason, so maybe it won't be as hard to identify >> them as I feared. I wonder whether we should envision this as "demote >> primary to standby" rather than an independent feature. > See my comments on the nearby pg_demote thread. I think we want both. Well, if pg_demote can be done for X amount of effort, and largely gets the job done, while this requires 10X or 100X the effort and introduces 10X or 100X as many bugs, I'm not especially convinced that we want both. regards, tom lane