Re: oid2name : add objects file path

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: David Bidoc <dcbidoc(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: oid2name : add objects file path
Date: 2026-01-14 05:24:56
Message-ID: 335f47af32e4042f9266c2b31d6ebc1aa0c22505.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2025-12-15 at 15:30 +0100, David Bidoc wrote:
> I attached the rebased and updated patch.

That patch looks good to me, and I think that is a useful addition.

If you want to display the path of databases as well, as you tried to
do in the original patch, I think the way to go would be to write a
new SQL function pg_database_filepath() similar to pg_relation_filepath().
That shouldn't be too hard - would you want to try that?

Other than that, you could try to propose a commit message and
prepare your patch with

git format-patch -v5 -1 -o /mypatches HEAD

after committing it to your branch. That would make the committer's
work easier.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2026-01-14 05:36:48 Re: [PATCH] test_aio: Skip io_uring tests when kernel disables it
Previous Message Soumya S Murali 2026-01-14 05:16:49 Re: InstallXLogFileSegment() vs concurrent WAL flush