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 1rZdu7-005dzh-NR for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Feb 2024 21:31:56 +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 1rZdu6-00DiRy-To for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Feb 2024 21:31:54 +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 1rZdu6-00DiRq-Ko for pgsql-hackers@lists.postgresql.org; Mon, 12 Feb 2024 21:31:54 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rZdu4-006sFH-0H for pgsql-hackers@lists.postgresql.org; Mon, 12 Feb 2024 21:31:54 +0000 Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2d107235bd0so948811fa.2 for ; Mon, 12 Feb 2024 13:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707773511; x=1708378311; darn=lists.postgresql.org; 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=+9hB1bsIKMSuLEHFOKT15kSsnpKwoHthfrh2k3yTpVE=; b=Rt4SfMChYxTLYBvywMWx7V8Qc7oCwmpfeXgApcv1Fwpz9Taz2n3EdeFfnSJGLu/Qwk l+BEI85yBYp2dvxtk0nQDfl3Hup4ApEFs3k1XAahix7+tUitt6uSY+ZKulalfr4OtjZ5 tLOLy6D9qlsKf1ypjkuKxivSnsZWa7Z4uDgkyQ44ZSAK9ESUZS2V5XxOKnSbTBTXKaAX eTzL5qUZ/+dSWMy0CzjpmhyyR1Abui00kJRnsMlxtFjJrX98fMGlIsec7aIAHGqmEoxK 7UldOIQRETQlOV3Iu1j/SHa9okEuzi9/WOpKpOd/07Le9eHgQm1MwAN1EmAM3DnJ8+Ir C77Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707773511; x=1708378311; 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=+9hB1bsIKMSuLEHFOKT15kSsnpKwoHthfrh2k3yTpVE=; b=a9sxGMeLtv05EINohkCBmfLoh/ah6im8LtHqSj8Pa5hQdCRiTOmlO3KrZ2lMtoIv+o Y0EBKIGFxwW672aLBjR+32nWYZpkjdFfiQF6zGSG9B8SfIY8z6vmhv462hMrrGFl0llU N2fx3n0CUcQu5mlh/yK1WZNKKS6euh7UQ8+jVIBTtjmiA9r2/N6ykZH3c4HA/fcB0IQn 96uWneWSnEsvokgvYi8ZWqkWJPRWU7dPi0DF/6/G+OGZLuXs4zGrq2GBgqg6ZA4g4+Ne 2hRXgpT/iVUrylHytHOhM8tMyPLTWP7xxcnOpQF++TsA6/g6q49ZtU85URBq/Q1SUXoA b3YQ== X-Forwarded-Encrypted: i=1; AJvYcCUr5I4syjLo/c1EFkC/wdjcvuQMNGD+dJSET2xFTS7K1g1EjXh+8I64DlJ8Dgk97F8iymwVoo6CaNjuk8tDG+nFgGdnnagCmwGoKcGPtkzVEm36 X-Gm-Message-State: AOJu0YxB1awgl6xd3Ecrut1hWtSjgMhKfNLgxkiX+CxbEh9tGwIdeYh7 wTBXeNfkFV0wkEZp/1VuZqBdQoLMtrHwbfOCNkQnmpsauqPZFUQQ1UDlRFJmp9Hc5c9UBstEjm7 lFAVt2KcqqfkQyoy5Ev6AUDfuxoDJOJNurAY= X-Google-Smtp-Source: AGHT+IHxmAn7+95038CamSo7PecbQ+I1Q1amcBtM7P+JbcjeTocuzduoORb1Aez+CDuHm82IVcOWWuqkwlKVCmWJJzM= X-Received: by 2002:a2e:980c:0:b0:2d0:aea9:d8d7 with SMTP id a12-20020a2e980c000000b002d0aea9d8d7mr4778167ljj.29.1707773511195; Mon, 12 Feb 2024 13:31:51 -0800 (PST) MIME-Version: 1.0 References: <772E8FE1-B1F7-4472-A132-06498B9D6907@yesql.se> <20240212204613.GA1815134@nathanxps13> In-Reply-To: From: Bharath Rupireddy Date: Tue, 13 Feb 2024 03:01:39 +0530 Message-ID: Subject: Re: Fix a typo in pg_rotate_logfile To: Daniel Gustafsson , dpage@pgadmin.org Cc: Nathan Bossart , 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 Tue, Feb 13, 2024 at 2:29=E2=80=AFAM Daniel Gustafsson = wrote: > > On that note though, we might want to consider just dropping it altogethe= r in > v17 (while fixing the incorrect hint in backbranches)? I can't imagine > adminpack 1.0 being in heavy use today, and skimming pgAdmin code it seem= s it's > only used in pgAdmin3 and not 4. Maybe it's time to simply drop old code? https://codesearch.debian.net/search?q=3Dpg_logfile_rotate&literal=3D1 shows no users for it though. There's pgadmin3 using it https://github.com/search?q=3Drepo%3Apgadmin-org%2Fpgadmin3%20pg_logfile_ro= tate&type=3Dcode, however the repo is archived. Surprisingly, core has to maintain the old code needed for adminpack 1.0 - pg_rotate_logfile_old SQL function and pg_rotate_logfile function in signalfuncs.c. These things could have been moved to adminpack.c back then and pointed CREATE FUNCTION pg_catalog.pg_logfile_rotate() to use it from adminpack.c. If we decide to remove adminpack 1.0 version completely, the 1.0 functions pg_file_read, pg_file_length and pg_logfile_rotate will also go away making adminpack code simpler. Having said that, it's good to hear from others, preferably from pgadmin developers - added Dave Page (dpage@pgadmin.org) in here for inputs. -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com