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 1ugOWY-002RMe-OQ for pgadmin-support@arkaria.postgresql.org; Mon, 28 Jul 2025 14:08:19 +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 1ugOWW-008CU5-Ru for pgadmin-support@arkaria.postgresql.org; Mon, 28 Jul 2025 14:08:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ugOP9-008Ar0-Lp for pgadmin-support@lists.postgresql.org; Mon, 28 Jul 2025 14:00:39 +0000 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ugOP8-001DSX-0D for pgadmin-support@lists.postgresql.org; Mon, 28 Jul 2025 14:00:39 +0000 Received: by mail-lj1-x232.google.com with SMTP id 38308e7fff4ca-32e14ce168eso49259471fa.1 for ; Mon, 28 Jul 2025 07:00:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753711236; x=1754316036; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2rJCCueBcO125xs2kwfeq63kV582snnsJ7OD27gBZxU=; b=ZyM51xmZeBYUCL49m4mLC1maZ9p/4ijwCTZGseLLFw4xTl8k8umY1ciEzdQbLgJt+Y 6klG5qt5tkNbngbV0mLfC0OABlqD2XzJsAlYXxWiWJCm5iNIJD4DZeKxUmcJNVlv6GEi qjLQE9auuIXHJLxCwvNv36Vw0MuLb/zye+uxcELQvUAhRaQW/OW6Tmb1EfnGbqyRAXZj WTzT3xi2Lps5tDRHU/AojJlYpYUDnnW5L1jyNsQcjFrIK+kIS0RKd8M2Ps1da9UGcjkq qsyIzC+qnWoBEPSQbVIPoZcw8IQSCYe7cqdF2AF8pDHQBnHxsDtKNPLZ6yEZgBriN342 XDBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753711236; x=1754316036; h=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=2rJCCueBcO125xs2kwfeq63kV582snnsJ7OD27gBZxU=; b=TUxKAA0lZqQuqicrb3EwxutXOEa0eEzcW5j6/UP2YbrcUXsU148cpLdcS38lxFwJcc 38dtXcGR3S/cgcGaHjZskeY9IG7xuBzg1t0wqQEtMEyXErb2jbubeEfhIkhBI4qiXAek IoBku22xSJoTS4hbsIqfHjipPVWQICbO7XUbOaIj2q3eGSr9dlg/ZSV+yuHsKEtjDId3 wUzsWosfmGU8Q5My3BNgfcBXrnrG9kPjKIJq5Fl2Hyy5G5giH60ciALmW/80G95a708A 73ie41Q05ra2xsSUA6CvPSOo9BCSSvV0PkcM/ECj+6Efq6zKF1/4LJU8EjE62nEQWOsT YNbA== X-Gm-Message-State: AOJu0YwYQXvYQWp+3sGZU45pShAqWN25MJwYr2xMuvPa5sm1y0IsqDic kLjP/IA8FtDzKpFNQprFlNX5e2aR329cNFTZe/pSTVL4ZJe23emcEBKVBiJznkplzNsgCDs+yHZ o02c+H7Z2sYts/sVA87NM27cALCA+OQ8= X-Gm-Gg: ASbGncsJ/aIz4VyX7yMF8I4+5fyPk+VWG1CGeptqf1NPv9iObp8kmZFke3nPreedqiX QU6GSdqBXrgaUKys7hU9jPBHPsj7etMWBvUsjmKKGQntPjLbHZ/4VDhwijeFVb8lmXCYTqUNvCp c8ep6RMC/oRfOBIWNSX0OIEMMjI2n36kpoWqFfRmwQ+0hccGfGmB1Pd4Ow3bpb5oRqPRYL8JWMT oS5mTqj80pi6a6gl21MHjisEGuJUKztSDjMgYY= X-Google-Smtp-Source: AGHT+IEAYr8TZkc6kYftwclI1wbjP7P8V0UEZdqSO5GqLb5n7K2Eh9f/OIZCJ7hObXWFK20LHOFFLdGEE7dYTHl4n7Q= X-Received: by 2002:a2e:b8d5:0:b0:32a:ec98:e14d with SMTP id 38308e7fff4ca-331ee680ee7mr32380551fa.16.1753711235739; Mon, 28 Jul 2025 07:00:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Abhinav Patni Date: Mon, 28 Jul 2025 19:30:24 +0530 X-Gm-Features: Ac12FXxI2SBDJJeRcxYGvzqJFKZ_PmnWrOGIRMYpWSYJz_YdPyvNAv41hOnB50I Message-ID: Subject: Re: Request to Remove Unused xmin Column from Function Properties Queries To: Dave Page Cc: pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000003eb6d7063afdb719" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003eb6d7063afdb719 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi I am seeing issues when using aurora postgres limitless. It doesn=E2=80=99t= support these columns, for function properties why do we need to query xmin value? Is it supporting some other use case? On Mon, 28 Jul 2025 at 7:28=E2=80=AFPM, Dave Page wrote= : > Hi > > On Mon, 28 Jul 2025 at 14:46, Abhinav Patni > wrote: > >> Dear pgAdmin Team, >> >> Queries for the xmin system column are causing errors and breaking >> function/property dialogs. > > > What errors or breakage do you see, and in what circumstances? Querying > for xmin shouldn't cause any issues on any supported PostgreSQL version, > even if it's not used. > > >> I see xmin is fetched in property queries >> (e.g.,=E2=80=AFfunctions/templates/*/properties.sql) but is always ignor= ed in >> processing, as in: >> >> >> web/pgadmin/browser/server_groups/servers/databases/schemas/functions/in= it.py: >> keys_to_ignore =3D ['oid', 'proowner', 'typnsp', 'xmin', =E2=80=A6] >> >> Can we drop xmin from these queries? Are there reasons to keep it? If >> not, would you accept a patch to remove it? >> >> Thanks, >> Abhinav Patni >> >> >> > > -- > Dave Page > pgAdmin: https://www.pgadmin.org > PostgreSQL: https://www.postgresql.org > pgEdge: https://www.pgedge.com > > --0000000000003eb6d7063afdb719 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0
I am seeing issues when u= sing aurora postgres limitless. It doesn=E2=80=99t support these columns, f= or function properties why do we need to query xmin value? Is it supporting= some other use case?

On Mon, 28 Jul 2025 at 7:28= =E2=80=AFPM, Dave Page <dpage@pgadm= in.org> wrote:
Hi
On = Mon, 28 Jul 2025 at 14:46, Abhinav Patni <abhinavpatni602@gmail.com> wrote:
Dear pgAdmin Team,

Queries for the xmin system column are causing errors and breaking
function/property dialogs.

What errors or = breakage do you see, and in what circumstances? Querying for xmin shouldn&#= 39;t cause any issues on any supported PostgreSQL version, even if it's= not used.
=C2=A0
I see xmin is fetched in property queries (e.g.,=E2=80=AFfunctions/templates/*/properties.sql) but is always ignored = in
processing, as in:

web/pgadmin/browser/server_groups/servers/databases/schemas/functions/init.= py:
keys_to_ignore =3D ['oid', 'proowner', 'typnsp', &#= 39;xmin', =E2=80=A6]

Can we drop xmin from these queries? Are there reasons to keep it? If
not, would you accept a patch to remove it?

Thanks,
Abhinav Patni




--
--0000000000003eb6d7063afdb719--