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>
 <CA+OCxoyx3yUNpzJ1q3hszUCJYzu0VpQGsR2JcLKUe3gofByauQ@mail.gmail.com>
 <4a993f44-b02c-449e-ab98-51f100aace66@darrenduncan.net>
In-Reply-To: <4a993f44-b02c-449e-ab98-51f100aace66@darrenduncan.net>
From: Dave Page <dpage@pgadmin.org>
Date: Tue, 29 Jul 2025 10:48:07 +0100
Message-ID: 
 <CA+OCxoy1sz58QW07ymGyKPcDyrtTn8-tYVui=LqeaRP5no_GPw@mail.gmail.com>
Subject: Re: Request to Remove Unused xmin Column from Function Properties
 Queries
To: Darren Duncan <darren@darrenduncan.net>
Cc: pgadmin-support@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000d81ff0063b0e4e00"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BOCxoy1sz58QW07ymGyKPcDyrtTn8-tYVui%3DLqeaRP5no_GPw%40mail.gmail.com>
Precedence: bulk

--000000000000d81ff0063b0e4e00
Content-Type: text/plain; charset="UTF-8"

On Tue, 29 Jul 2025 at 10:24, Darren Duncan <darren@darrenduncan.net> wrote:

> I had understood that Aurora mainly differed with its lower level
> internals
> implementation, but that it should look the same from a user perspective
> and
> thus be drop-in compatible with regular Postgres in practice, such that
> any
> database schemas or clients that work in regular should work with it
> unmodified.
>
> What are the main differences you see in Aurora that are surfaced to users
> such
> that they would have any kinds of impact on pgAdmin compatibility?
>

Things related to the underlying storage engine like system columns on
tables, for example xmin/xmax/ctid which might be different, but there are
also a bunch of unsupported features (
https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-unsupported-features.html),
none of which pgAdmin knows are unsupported or in what way - e.g. are there
system catalogues that are missing, will DDL be accepted but do nothing or
will it throw errors, will some of the catalogues be missing individual
columns that may not be needed because certain features are unsupported?
The list is likely longer than that, but you get the gist.

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

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 29 Jul =
2025 at 10:24, Darren Duncan &lt;<a href=3D"mailto:darren@darrenduncan.net"=
>darren@darrenduncan.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I had und=
erstood that Aurora mainly differed with its lower level internals <br>
implementation, but that it should look the same from a user perspective an=
d <br>
thus be drop-in compatible with regular Postgres in practice, such that any=
 <br>
database schemas or clients that work in regular should work with it unmodi=
fied.<br>
<br>
What are the main differences you see in Aurora that are surfaced to users =
such <br>
that they would have any kinds of impact on pgAdmin compatibility?<br></blo=
ckquote><div><br></div><div>Things related to the underlying storage engine=
 like system columns on tables, for example xmin/xmax/ctid which might be d=
ifferent, but there are also a bunch of unsupported features (<a href=3D"ht=
tps://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgre=
sql-compatibility-unsupported-features.html">https://docs.aws.amazon.com/au=
rora-dsql/latest/userguide/working-with-postgresql-compatibility-unsupporte=
d-features.html</a>), none of which pgAdmin knows are unsupported or in wha=
t way - e.g. are there system catalogues that are missing, will DDL be acce=
pted but do nothing or will it throw errors, will some of the catalogues be=
 missing individual columns that may not be needed because certain features=
 are unsupported? The list is likely longer than that, but you get the gist=
.</div><div><br></div></div><span class=3D"gmail_signature_prefix">-- </spa=
n><br><div dir=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.postgresq=
l.org" target=3D"_blank">https://www.postgresql.org</a></div><div>pgEdge: <=
a href=3D"https://www.pgedge.com" target=3D"_blank">https://www.pgedge.com<=
/a><br><div></div><div><br></div></div></div></div></div>

--000000000000d81ff0063b0e4e00--