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 1nIV84-0001Jc-UF for pgsql-bugs@arkaria.postgresql.org; Fri, 11 Feb 2022 12:34:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIV83-0003rO-3P for pgsql-bugs@arkaria.postgresql.org; Fri, 11 Feb 2022 12:34:23 +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 1nIV82-0003rE-OK for pgsql-bugs@lists.postgresql.org; Fri, 11 Feb 2022 12:34:22 +0000 Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nIV7v-0005AC-90 for pgsql-bugs@lists.postgresql.org; Fri, 11 Feb 2022 12:34:21 +0000 Received: by mail-pj1-x102c.google.com with SMTP id r64-20020a17090a43c600b001b8854e682eso8761063pjg.0 for ; Fri, 11 Feb 2022 04:34:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=sabSRUIXy2Loh/GpQRPsLAa93K8aRwwUeRQLlXOsxik=; b=qi1XSHYXnVCTnuzrJC+XCBHn8AyJgb1kZLvk7qpjzzWdNVGVr12KoneoMLsWSdigbl xBRRWpTKzDpPar3st6+5/GoEjh1PyOSI10UPstHfTCD5JFOWQTyOG+rHmO6wKZ9ai0Er tIVnuf8RaZm0VzW60BFUkF4myh1ww9Yj8VH44K11DRUbBDsrYjDjlgEIYhSYo6s5RDHB ICRimiOmekckElFr81gD/ukR1fZFiAoF3+BNWlPcS9Kf2ousRo0zr+JGM25N6eai5T65 dhRPgUCwrUhWmqCPDiNi6LsML+Fo2GGQB5frE06vqgZXrLX1EOrMjrHp53IhLwdRhZJ/ Yesw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=sabSRUIXy2Loh/GpQRPsLAa93K8aRwwUeRQLlXOsxik=; b=fRXyxOjg/igqu04RpjCqUTcwVHf86vD/UJ2ENnTPRlJ0DTx0qJ2ZhrfxuZ/wEICh6y SLpr/hBg2jXlE08TI7Qau1PDzjSyve5jRm0DFGdCvKLKnzka5zDEkj3BaCFhKBLiAhCJ 0+8/UaV57sxJmFBLl0o6wrrqz5gl/YrfgAN5402xlryxJpK2CvPTCaor31XHo/rWkTTn ANT5My3o/rpmabI8PiIfExWmJazgAI8hFl8NFk/8SdvKg2DxF90qrprwMxT1yMCvhG9O teZhEKyqOg7yLwDRwFjSnY6c3+ZpD3FomiqUL0PjWaao/HqGhG28qYztKxzsHcSIcMsz j4+w== X-Gm-Message-State: AOAM53021a0U0xWvhUAIbqhSUcJoEwewkxAmylTSq1bnrGkWT5Ni3iAU CSfXnGc77yBFLcS8hJ7uIAE= X-Google-Smtp-Source: ABdhPJznqw/L6aJr8KBet+fRQ6I4QVLiHoJ1qDQY78r/P2PPYZ2mwXKo9fvb9Aup5TPB+RVc4QFPTA== X-Received: by 2002:a17:90a:ce08:: with SMTP id f8mr144917pju.27.1644582854182; Fri, 11 Feb 2022 04:34:14 -0800 (PST) Received: from jrouhaud (2001-b011-1005-5f8d-a9a6-2e36-1a11-d328.dynamic-ip6.hinet.net. [2001:b011:1005:5f8d:a9a6:2e36:1a11:d328]) by smtp.gmail.com with ESMTPSA id p4sm7971928pgh.53.2022.02.11.04.34.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Feb 2022 04:34:13 -0800 (PST) Date: Fri, 11 Feb 2022 20:34:09 +0800 From: Julien Rouhaud To: "Agarwal, Pragati - Dell Team" Cc: Merlin Moncure , "pgsql-bugs@lists.postgresql.org" , "Silaparasetti, Ramesh" , "Kishore, Nanda - Dell Team" , "Mahendrakar, Prabhakar - Dell Team" Subject: Re: Very URGENT REQUEST - Postgresql error : PANIC: could not locate a valid checkpoint record Message-ID: <20220211123409.2dwm64ppgzfopyta@jrouhaud> References: <20220210144450.o5nd6gcdt7qlittt@jrouhaud> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Feb 11, 2022 at 11:19:54AM +0000, Agarwal, Pragati - Dell Team wrote: > Hi Merlin, Julien > > Thanks for your response. > > Besides this, there is public schema in postgres which we are not using in > our Datastore service. > > As a workaround of an upgrade process, we plan to drop the public schema. We > would like to know your thoughts on this and any detrimental impact on the > data or service. I'm not sure how that's a workaround, but that schema isn't necessary for postgres, it's just a schema that's created by default. You can remove it without impact as long as you don't rely on it in any of your applications.