Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJvV7-007O0V-8T for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jun 2024 13:37:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJvV4-00GebC-Im for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jun 2024 13:37:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJvV4-00Geag-8b for pgsql-hackers@lists.postgresql.org; Wed, 19 Jun 2024 13:37:23 +0000 Received: from mail-io1-xd2c.google.com ([2607:f8b0:4864:20::d2c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJvV3-002TP3-0H for pgsql-hackers@postgresql.org; Wed, 19 Jun 2024 13:37:22 +0000 Received: by mail-io1-xd2c.google.com with SMTP id ca18e2360f4ac-7ea0b5e0977so304749339f.2 for ; Wed, 19 Jun 2024 06:37:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718804239; x=1719409039; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=A2gSz2n7jVkoI0Wb3/OfwZUNXe2g7vquU1E3qI+R3zA=; b=LcB5MvhzVD2PWBdUOu+6hh3oAivE5BjjhqpuMW0qRglslc/u10arBCo2b51oAQ4b2T d+fa5Eo8U/svc+SfFkWO9r05uEcaKlewcwU/Zwu+fUHC4lowa2mDo52nkqu4OfDo5LAV unywgw6ubmgz3QW/vp414Npt+DMdbSe1zDLpJNdL7IFwuo4dX2iDWevDTMXSOV2gIV4O wAJkHY9iwebqR7wHMjJYCsatSncPHuQ/A1zptZlE+WmxEjyK0eM709Bd5UdQ7LggVHWk RH/ktIqoVWGR30eMqkst6NRD4Su9lk4nAdGDVqMwY+nhUCR0DgGLV65zK8E5j+k/b7RF yGmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718804239; x=1719409039; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=A2gSz2n7jVkoI0Wb3/OfwZUNXe2g7vquU1E3qI+R3zA=; b=ERrBOPiFFD7twFB+6m6DrlE8WNa4b5k1iOyl/VZcm9LTfh44gLRR3Bsf2pbVoS3Bs4 Oia8Ukquu7Exo+8620NtvSsPz/c3YDiGqy68IyfQUFnEu+j/xA3pEEOFrzZ7RR4gc3Ut pZ0MCSMjUyWFw2k2t131fU+w+ZnazSBiqxV0qnNkF+PHqzlpsCaC0wQ2plVJgr6huOXM CbhOlbXFKl2Pe3bVyQmkmTkvOJroPHdvmEh44X7pJAMbZY8uTtExWerrHdKbxiM0BJ2o accY1RbUXr3Y73jVTcNTmgHEQPU3xFpWd2awMsSmrakLR5Dpthoxe/dpcQxFYu2/s7xu gdxQ== X-Forwarded-Encrypted: i=1; AJvYcCVkanBzvYEB7cXPiKaRrm2brA2Twzd+kGwhMZD8fVPriYLwdCRri58eDMW7EZOkLBVEOIYfbhdvk2D+NwfSpkW0AEsPZJggSgbrdt7B X-Gm-Message-State: AOJu0YzVAkm5wn01I6ycm89Dyovu0gIThS81a9gPkq0jMsDFwLarI3Hj ymxPfRycd2Q8P3TcRrmI9GpeZJafJKfH6BzzCgfiy0/t3D6PlDzT X-Google-Smtp-Source: AGHT+IFLeBOFRL1oTzkj9XeVFHq0pV4tFZ4KqV7hfGpwd5+xwBkduJZqukcoRlLpgoIFbJPaW43rjw== X-Received: by 2002:a05:6602:3fc9:b0:7de:c720:ab1f with SMTP id ca18e2360f4ac-7f13ee82ac8mr309041439f.20.1718804238937; Wed, 19 Jun 2024 06:37:18 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4b9569ef7d5sm3899458173.85.2024.06.19.06.37.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Jun 2024 06:37:18 -0700 (PDT) Date: Wed, 19 Jun 2024 08:37:17 -0500 From: Nathan Bossart To: Robert Haas Cc: Matthias van de Meent , Dilip Kumar , Ranier Vilela , pgsql-hackers@postgresql.org Subject: Re: use CREATE DATABASE STRATEGY = FILE_COPY in pg_upgrade Message-ID: References: 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 Wed, Jun 19, 2024 at 09:17:00AM -0400, Robert Haas wrote: > OK, I have a (probably) stupid question. The comment says: > > + * In binary upgrade mode, we can skip this checkpoint because neither of > + * these problems applies: we don't ever replay the WAL generated during > + * pg_upgrade, and we don't concurrently modify template0 (not to mention > + * that trying to take a backup during pg_upgrade is pointless). > > But what happens if the system crashes during pg_upgrade? Does this > patch make things worse than they are today? And should we care? My understanding is that you basically have to restart the upgrade from scratch if that happens. I suppose there could be a problem if you try to use the half-upgraded cluster after a crash, but I imagine you have a good chance of encountering other problems if you do that, too. So I don't think we care... -- nathan