| 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-28 13:57:53 |
| Message-ID: | CA+OCxox8fKAwNObF=LeW7b1oA+nLyg3g8MmJ1ftMe-yyqeXNvQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi
On Mon, 28 Jul 2025 at 14:46, Abhinav Patni <abhinavpatni602(at)gmail(dot)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 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-28 14:00:24 | Re: Request to Remove Unused xmin Column from Function Properties Queries |
| Previous Message | Abhinav Patni | 2025-07-28 13:21:06 | Request to Remove Unused xmin Column from Function Properties Queries |