Re: oid2name : add objects file path

David Bidoc <dcbidoc@gmail.com>

From: David Bidoc <dcbidoc@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Guillaume Lelarge <guillaume.lelarge@dalibo.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-12-15T14:30:53Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. oid2name: Add relation path to the information provided by -x/--extended

Attachments

Hi Michael

On Thu, Dec 4, 2025 at 1:46 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Tue, Dec 02, 2025 at 11:36:39AM +0100, David Bidoc wrote:
> > I attached the rebased patch.
> > Any feedback would be appreciated.
>
> Your patch still fails to apply on HEAD for all the changes of
> contrib/oid2name/oid2name.c.  Please see the following:
> https://commitfest.postgresql.org/patch/6111/
>

Thank you for your feedback.
I attached the rebased and updated patch.

> It also seems like Euler's feedback has not been answered.  I am
> pretty sure that he was referring about the addition of an example in
> the documentation, or at least refreshing the areas of the docs that
> are impacted with your change (no clear idea about all that without a
> rebased patch).

I updated the documentation example about the -x option :

$ # you can mix the options, and get more details with -x
$ oid2name -d alvherre -t accounts -f 1155291 -x
>From database "alvherre":
  Filenode     Table Name      Oid  Schema  Tablespace            Filepath
--------------------------------------------------------------------------
    155173       accounts   155173  public  pg_default   base/17228/155173
   1155291  accounts_pkey  1155291  public  pg_default  base/17228/1155291

I modified the example already used to maintain consistency.

--
David Bidoc