Re: Request to Remove Unused xmin Column from Function Properties Queries

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?

Darren Duncan

On 2025-07-29 1:37 a.m., Dave Page wrote:
> Hi
> 
> On Mon, 28 Jul 2025 at 15:00, Abhinav Patni wrote:
> 
>     Hi
>     I am seeing issues when using aurora postgres limitless. It doesn’t support
>     these columns, for function properties why do we need to query xmin 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 <https://github.com/pgadmin-org/pgadmin4>
> 
> Thanks!
> -- 
> 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>
>