Re: Request to Remove Unused xmin Column from Function Properties Queries
От | Abhinav Patni |
---|---|
Тема | Re: Request to Remove Unused xmin Column from Function Properties Queries |
Дата | |
Msg-id | CAJRqHc+yu=bPSADbfw6r8b_Jmu0yiHaP-iXxPmYdC5w4L36dqA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Request to Remove Unused xmin Column from Function Properties Queries (Dave Page <dpage@pgadmin.org>) |
Список | pgadmin-support |
Hi Dave, Thanks for your prompt response and for clarifying the situation. I appreciate your guidance! For this particular use case, I'll move forward with the fix as discussed. If I encounter other incompatibilities, I'll reach out or look into them further. Thanks again! On Tue, Jul 29, 2025 at 2:07 PM Dave Page <dpage@pgadmin.org> wrote: > > 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’t support these columns, for function properties whydo 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 (whichseems likely), then I don't see any reason not to remove it from the query, but there will likely be other ways inwhich 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://www.postgresql.org > pgEdge: https://www.pgedge.com >
В списке pgadmin-support по дате отправления: