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 | CAJRqHcKbSYUn5=odJav_5M66xosUbgFyrhEF2e5_9iMyXfRjAw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Request to Remove Unused xmin Column from Function Properties Queries (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: Request to Remove Unused xmin Column from Function Properties Queries
|
Список | pgadmin-support |
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?
On Mon, 28 Jul 2025 at 7:28 PM, Dave Page <dpage@pgadmin.org> wrote:
HiOn Mon, 28 Jul 2025 at 14:46, Abhinav Patni <abhinavpatni602@gmail.com> wrote:Dear pgAdmin Team,
Queries for the xmin system column are causing errors and breaking
function/property dialogs.What errors or breakage do you see, and in what circumstances? Querying for xmin shouldn't cause any issues on any supported PostgreSQL version, even if it's not used.I see xmin is fetched in property queries
(e.g., functions/templates/*/properties.sql) but is always ignored in
processing, as in:
web/pgadmin/browser/server_groups/servers/databases/schemas/functions/init.py:
keys_to_ignore = ['oid', 'proowner', 'typnsp', 'xmin', …]
Can we drop xmin from these queries? Are there reasons to keep it? If
not, would you accept a patch to remove it?
Thanks,
Abhinav Patni--Dave PagepgAdmin: https://www.pgadmin.orgPostgreSQL: https://www.postgresql.org
В списке pgadmin-support по дате отправления: