MIME-Version: 1.0
References: 
 <CAJRqHcJpf2thrFTw_092nGWAvU3Du9_eXbOOG62U9oBZOUpLgg@mail.gmail.com>
 <CA+OCxox8fKAwNObF=LeW7b1oA+nLyg3g8MmJ1ftMe-yyqeXNvQ@mail.gmail.com>
 <CAJRqHcKbSYUn5=odJav_5M66xosUbgFyrhEF2e5_9iMyXfRjAw@mail.gmail.com>
In-Reply-To: 
 <CAJRqHcKbSYUn5=odJav_5M66xosUbgFyrhEF2e5_9iMyXfRjAw@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Tue, 29 Jul 2025 09:37:27 +0100
Message-ID: 
 <CA+OCxoyx3yUNpzJ1q3hszUCJYzu0VpQGsR2JcLKUe3gofByauQ@mail.gmail.com>
Subject: Re: Request to Remove Unused xmin Column from Function Properties
 Queries
To: Abhinav Patni <abhinavpatni602@gmail.com>
Cc: pgadmin-support@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000001ef920063b0d523f"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BOCxoyx3yUNpzJ1q3hszUCJYzu0VpQGsR2JcLKUe3gofByauQ%40mail.gmail.com>
Precedence: bulk

--0000000000001ef920063b0d523f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi

On Mon, 28 Jul 2025 at 15:00, Abhinav Patni <abhinavpatni602@gmail.com>
wrote:

> 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 xm=
in
> value? Is it supporting some other use case?
>

Aurora isn't something we support, as it's different from PostgreSQL in
many ways. If xmin isn't used in this case (which seems likely), then I
don't see any reason not to remove it from the query, but there will likely
be other ways in which pgAdmin won't work properly with Aurora, that may
not be so easy to fix.

Please feel free to submit a pull request at
https://github.com/pgadmin-org/pgadmin4

Thanks!

--=20
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com

--0000000000001ef920063b0d523f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote gmail_quote_con=
tainer"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 28 Jul 2025 at 15:00,=
 Abhinav Patni &lt;<a href=3D"mailto:abhinavpatni602@gmail.com">abhinavpatn=
i602@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:sol=
id;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">H=
i=C2=A0</div><div dir=3D"auto">I am seeing issues when using aurora postgre=
s limitless. It doesn=E2=80=99t support these columns, for function propert=
ies why do we need to query xmin value? Is it supporting some other use cas=
e?</div></blockquote><div><br></div><div>Aurora isn&#39;t something we supp=
ort, as it&#39;s different from PostgreSQL in many ways. If xmin isn&#39;t =
used in this case (which seems likely), then I don&#39;t see any reason not=
 to remove it from the query, but there will likely be other ways in which =
pgAdmin won&#39;t work properly with Aurora, that may not be so easy to fix=
.=C2=A0</div><div><br></div><div>Please feel free to submit a pull request =
at=C2=A0<a href=3D"https://github.com/pgadmin-org/pgadmin4">https://github.=
com/pgadmin-org/pgadmin4</a></div><div><br></div><div>Thanks!</div><div>=C2=
=A0</div></div><span class=3D"gmail_signature_prefix">-- </span><br><div di=
r=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Dave Page<div>pgAdmin:=
 <a href=3D"https://www.pgadmin.org" target=3D"_blank">https://www.pgadmin.=
org</a></div><div>PostgreSQL: <a href=3D"https://www.postgresql.org" target=
=3D"_blank">https://www.postgresql.org</a></div><div>pgEdge: <a href=3D"htt=
ps://www.pgedge.com" target=3D"_blank">https://www.pgedge.com</a><br><div><=
/div><div><br></div></div></div></div></div>

--0000000000001ef920063b0d523f--