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 1uSkAT-00CW9g-PQ for pgsql-committers@arkaria.postgresql.org; Fri, 20 Jun 2025 22:25:05 +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 1uSkAR-004dih-Hz for pgsql-committers@arkaria.postgresql.org; Fri, 20 Jun 2025 22:25:04 +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 1uSkAR-004diY-AX for pgsql-committers@lists.postgresql.org; Fri, 20 Jun 2025 22:25:03 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uSkAP-003Djj-1B; Fri, 20 Jun 2025 22:25:03 +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 55KMOxaM2585994; Fri, 20 Jun 2025 18:24:59 -0400 From: Tom Lane To: Melanie Plageman cc: Alexander Korotkov , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Improve runtime and output of tests for replication slots checkp In-reply-to: <2542023.1750456985@sss.pgh.pa.us> References: <2542023.1750456985@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 20 Jun 2025 18:03:05 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2585992.1750458298.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Jun 2025 18:24:58 -0400 Message-ID: <2585993.1750458298@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > But in the buildfarm failures I don't see any 'checkpoint complete' > before the shutdown. Ooops, I lied: we have at least one case where the checkpoint does finish but then it hangs up anyway: https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=3Dmelonworm&= dt=3D2025-06-20%2019%3A59%3A31&stg=3Drecovery-check 2025-06-20 20:05:32.548 UTC [3171474][client backend][61/2:0] LOG: statem= ent: select injection_points_wakeup('checkpoint-before-old-wal-removal') 2025-06-20 20:05:32.550 UTC [3162113][checkpointer][:0] LOG: checkpoint c= omplete: wrote 1 buffers (0.0%), wrote 0 SLRU buffers; 0 WAL file(s) added= , 0 removed, 0 recycled; write=3D0.045 s, sync=3D0.001 s, total=3D1.507 s;= sync files=3D1, longest=3D0.001 s, average=3D0.001 s; distance=3D327688 k= B, estimate=3D327688 kB; lsn=3D0/290020C0, redo lsn=3D0/29002068 2025-06-20 20:05:32.551 UTC [3171474][client backend][:0] LOG: disconnect= ion: session time: 0:00:00.073 user=3Dbf database=3Dpostgres host=3D[local= ] 2025-06-20 20:05:32.552 UTC [3170563][client backend][:0] LOG: disconnect= ion: session time: 0:00:01.538 user=3Dbf database=3Dpostgres host=3D[local= ] 2025-06-20 20:05:32.564 UTC [3163446][client backend][7/146:0] LOG: state= ment: SELECT 1 = 2025-06-20 20:05:32.564 UTC [3161873][postmaster][:0] LOG: received immed= iate shutdown request 2025-06-20 20:05:32.604 UTC [3161873][postmaster][:0] LOG: database syste= m is shut down I'm still confused about whether the 046 script intends to sometimes test cases where the checkpoint doesn't have time to complete. But it seems that whatever is going on here is a bit subtle and platform-dependent. regards, tom lane