public inbox for [email protected]
help / color / mirror / Atom feedFrom: Darren Duncan <[email protected]>
To: [email protected]
Subject: Re: Request to Remove Unused xmin Column from Function Properties Queries
Date: Tue, 29 Jul 2025 03:18:03 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+OCxoy1sz58QW07ymGyKPcDyrtTn8-tYVui=LqeaRP5no_GPw@mail.gmail.com>
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>
<[email protected]>
<CA+OCxoy1sz58QW07ymGyKPcDyrtTn8-tYVui=LqeaRP5no_GPw@mail.gmail.com>
So it looks like there are at least 2 distinct versions of Postgres-compatible
Amazon Aurora.
The regular Aurora would have all the regular Postgres features I suppose.
While the one you linked to is a specialized Distributed or DSQL variant and I
see it is actually missing a huge amount of standard features, including foreign
keys, sequences, triggers, exclusion constraints, and mixing DDL and DML in a
common transaction.
Darren Duncan
On 2025-07-29 2:48 a.m., Dave Page wrote:
> On Tue, 29 Jul 2025 at 10:24, Darren Duncan 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 <https://www.pgadmin.org;
> PostgreSQL: https://www.postgresql.org <https://www.postgresql.org;
> pgEdge: https://www.pgedge.com <https://www.pgedge.com;
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Request to Remove Unused xmin Column from Function Properties Queries
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox