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 1q8ABg-0002YJ-3g for pgsql-hackers@arkaria.postgresql.org; Sun, 11 Jun 2023 01:48:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q8ABe-0008G7-U4 for pgsql-hackers@arkaria.postgresql.org; Sun, 11 Jun 2023 01:48:10 +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 1q8ABe-0008Fy-KJ for pgsql-hackers@lists.postgresql.org; Sun, 11 Jun 2023 01:48:10 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q8ABb-001X0u-OP for pgsql-hackers@lists.postgresql.org; Sun, 11 Jun 2023 01:48:10 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2b1b084620dso35342561fa.0 for ; Sat, 10 Jun 2023 18:48:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686448086; x=1689040086; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Fr+s8pz/kWXocHGbAZv95vFzSlwws+UU/t3MQquRnIs=; b=HT5mX+okkW6RpJ5Ss1Ss4qYuPUoKH8/jG9S8hS2JxW8DpwaNm1URI72FnLqxTlkhn0 XXv38hAYuZcwZ9NDdwclvEhWQ84GIUbCbJNX8Vhuu0bdLpt1AmV28Hs0+o3qn4NgqnF/ sRaXKZMn1GDmj+4RROx4O8kyRZfYAAIEo0hgVKT1nrWoHcq6A0K+0PJe/3FVjkNMM2I3 NR/hDEWrsaEW6IlV595A6oF+yzRoMUb6qXBDkIru35gtLW7XPP7COqA/jM+G4gTrQi25 AzBeiN6wgXlCeBuxa/pg688rga+D5QuN0ZUfPIpnk4XqzhlBapQ0/beRsE5qhkUq1Wne oRQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686448086; x=1689040086; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Fr+s8pz/kWXocHGbAZv95vFzSlwws+UU/t3MQquRnIs=; b=XNUQrZNGoKY+2zgoSkFooJVBZcWaDbJ58sSNlhZZcNvKnZedIiKZ08/q0oscwdoQJE 8hMhjojikkvfOIhXpg9HgtR8r6BZewDAF7ADzltTFhcI0OUAW4oAnBXJO+nhXizb41ed 3TlSkg7SlLHmxI9NHlBYV2dg3WaS0V8/0KhDenWyAFIsUmStH+sKGkdPJXliIZRPoDkk S2PCAQErshD0I/ts+SpJdb0teSiPsljoTeItHy7u7UADLETMtfiCu7ZlXmwd1h5kXHVr cQ2X4vwzY0gZ2qVhwhrVtAT+M7pRMXVRx3ZRlOXlviQZKwJtrnVS1V7ejpLXnuSHw2xX Gpxw== X-Gm-Message-State: AC+VfDwmeGRq4hcjWz0ZKs0sE9rvd/2cH5DCTd0xQ0cydcD3p2nowtQF OZxhAkhx2YBHNWUgaC4AMzUyUxvGacPQ8ckuYig= X-Google-Smtp-Source: ACHHUZ6qetT84XXLCkXDSL/4mgxC//9KcBrW5O9gLybJvamPFvdeow/voDsLHcFnI4503PbivQ1+AkZS1In9dr3Qc9A= X-Received: by 2002:a2e:3809:0:b0:2b2:52:7eea with SMTP id f9-20020a2e3809000000b002b200527eeamr1076161lja.48.1686448085998; Sat, 10 Jun 2023 18:48:05 -0700 (PDT) MIME-Version: 1.0 References: <87cz2otiw3.fsf@wibble.ilmari.org> In-Reply-To: From: Bharath Rupireddy Date: Sun, 11 Jun 2023 07:17:55 +0530 Message-ID: Subject: Re: Implement generalized sub routine find_in_log for tap test To: Michael Paquier Cc: vignesh C , Andrew Dunstan , =?UTF-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jun 9, 2023 at 8:29=E2=80=AFAM Michael Paquier wrote: > > On Tue, Jun 06, 2023 at 05:53:40PM +0530, Bharath Rupireddy wrote: > > Yes. A simpler way of doing it would be to move advance_wal() in > > 019_replslot_limit.pl to Cluster.pm, something like the attached. CI > > members don't complain with it > > https://github.com/BRupireddy/postgres/tree/add_a_function_in_Cluster.p= m_to_generate_WAL. > > Perhaps, we can name it better instead of advance_wal, say > > generate_wal or some other? > > Why not discussing that on a separate thread? What you are proposing > is independent of what Vignesh has proposed. Sure. Here it is - https://www.postgresql.org/message-id/CALj2ACU3R8QFCvDewHCMKjgb2w_-CMCyd6DA= K%3DJb-af14da5eg%40mail.gmail.com. > Note that the patch > format is octet-stream, causing extra CRs to exist in the patch. > Something happened on your side when you sent your patch, I guess? Had to attach the patch in .txt format to not block Vignesh's patch from testing by CF Bot (if at all this thread was added there). -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com