| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Abhinav Patni <abhinavpatni602(at)gmail(dot)com> |
| Cc: | pgadmin-support(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Request to Remove Unused xmin Column from Function Properties Queries |
| Date: | 2025-07-29 08:37:27 |
| Message-ID: | CA+OCxoyx3yUNpzJ1q3hszUCJYzu0VpQGsR2JcLKUe3gofByauQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi
On Mon, 28 Jul 2025 at 15:00, Abhinav Patni <abhinavpatni602(at)gmail(dot)com>
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
Thanks!
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://stream.boxwatch.ru
pgEdge: https://www.pgedge.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhinav Patni | 2025-07-29 08:59:55 | Re: Request to Remove Unused xmin Column from Function Properties Queries |
| Previous Message | Stephen Davies | 2025-07-29 07:44:25 | Problem using new installation |