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 1joi7c-0008GF-Mk for pgsql-hackers@arkaria.postgresql.org; Fri, 26 Jun 2020 06:46:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1joi7b-000719-J4 for pgsql-hackers@arkaria.postgresql.org; Fri, 26 Jun 2020 06:45:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1joi7b-000712-CF for pgsql-hackers@lists.postgresql.org; Fri, 26 Jun 2020 06:45:59 +0000 Received: from mail-ed1-f66.google.com ([209.85.208.66]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1joi7Y-000473-8R for pgsql-hackers@postgresql.org; Fri, 26 Jun 2020 06:45:59 +0000 Received: by mail-ed1-f66.google.com with SMTP id e15so6075697edr.2 for ; Thu, 25 Jun 2020 23:45:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:to:cc:subject:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=uruHZWhzvxCGgFpedX5qu9knbrW7gHij14HwV1fW4MQ=; b=KeyhTWJlP2c2KlN/PK+g5AvnEVGa43iBkBYwZP6CdvkoVO9UF8BPRBC1z9mPmr4koE UY+UjhbZl5ILc3Wa80eWOc93Mz0qjrjZO0nmfnB+8K2pe431vQRqixzbY5EPGMCRi5Ka vwb3FuSmDevnHOQXM+2n6aJ9bqHywh23igpoAzv7l7ujLX6WuDPlXGGTRC6CQZK1QpZm 3Hiv+fyBEQyG1mozUr++ycAzylNqZIng/scEgb6VhNnqxSKZpougyJdofQzr3jIzweCm j7quvHxGDG00663YDmgLqIcah8Fk7kR/dxQF31QJQYCVfYOqPkj38iMUR2KIs0y+l3Y8 83rQ== X-Gm-Message-State: AOAM533wjHJHhdt3ej05XyNd7nVMu54DylzY3Q51NrODl6/PMzuzGObG 4uxteqo0NLQGz+20SKsSUeA= X-Google-Smtp-Source: ABdhPJyOBv5udGysBw4h4zO/+esldsN88cxkYy4ymmaFbp7HQRVDOk8+Ng4g6Gk9LDtLSEkzZTs+xQ== X-Received: by 2002:a05:6402:94f:: with SMTP id h15mr1875477edz.313.1593153955319; Thu, 25 Jun 2020 23:45:55 -0700 (PDT) Received: from hartree.caipicrew.dd-dns.de ([2001:a61:3b15:2301:221:86ff:fea2:57e7]) by smtp.gmail.com with ESMTPSA id l8sm18422821ejc.85.2020.06.25.23.45.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Jun 2020 23:45:54 -0700 (PDT) Message-ID: <5ef599a2.1c69fb81.f8b1d.dd8a@mx.google.com> X-Google-Original-Message-ID: <20200626064553.GA27884@caipicrew.dd-dns.de;hartree.caipicrew.dd-dns.de> Received: from mbanck by hartree.caipicrew.dd-dns.de with local (Exim 4.92) (envelope-from ) id 1joi7V-0002iy-Ht; Fri, 26 Jun 2020 08:45:53 +0200 Date: Fri, 26 Jun 2020 08:45:53 +0200 From: Michael Banck To: tushar Cc: Amul Sul , Robert Haas , Amit Kapila , PostgreSQL-development Subject: Re: [Patch] ALTER SYSTEM READ ONLY References: 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.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On Wed, Jun 24, 2020 at 01:54:29PM +0530, tushar wrote: > On 6/22/20 11:59 AM, Amul Sul wrote: > > 2. Now skipping the startup checkpoint if the system is read-only mode, as > > discussed [2]. > > I am not able to perform pg_checksums o/p after shutting down my server in > read only  mode . > > Steps - > > 1.initdb (./initdb -k -D data) > 2.start the server(./pg_ctl -D data start) > 3.connect to psql (./psql postgres) > 4.Fire query (alter system read only;) > 5.shutdown the server(./pg_ctl -D data stop) > 6.pg_checksums > > [edb@tushar-ldap-docker bin]$ ./pg_checksums -D data > pg_checksums: error: cluster must be shut down > [edb@tushar-ldap-docker bin]$ What's the 'Database cluster state' from pg_controldata at this point? Michael -- Michael Banck Projektleiter / Senior Berater Tel.: +49 2166 9901-171 Fax: +49 2166 9901-100 Email: michael.banck@credativ.de credativ GmbH, HRB Mönchengladbach 12080 USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer Unser Umgang mit personenbezogenen Daten unterliegt folgenden Bestimmungen: https://www.credativ.de/datenschutz