Re: Add starelid, attnum to pg_stats and leverage this in pg_dump - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Date
Msg-id CADkLM=d-yUR8JsM-UmCfeRAhVj+X9MYi0kz9=zQO4EoBkd8H8A@mail.gmail.com
Whole thread
In response to Re: Add starelid, attnum to pg_stats and leverage this in pg_dump  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
List pgsql-hackers
On Tue, Mar 10, 2026 at 12:42 PM Corey Huinker <corey.huinker@gmail.com> wrote:


On Tue, Mar 10, 2026 at 12:37 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
On Mon, Mar 09, 2026 at 06:42:46PM -0400, Corey Huinker wrote:
> If you want 0003 split into two (one for pg_stats_ext and one for
> pg_stats_ext_exprs) I can do that, but they felt like a package deal to me.

Sorry to throw a curveball here, but I think the best way to structure this
patch set is as follows:

* 0001: Just the test changes (e.g., replacing * with column lists).  By
doing that first, the actual functionality changes in 0002 will be easier
to see.

Makes sense.
 

* 0002: Adding columns to the all the views (this one will do a catalog
bump).  If we need to make a couple of test adjustments to verify the OIDs
or attribute IDs, that's fine, but those can be pretty minimal.

So all three views in one go. +1
 

* 0003: Associated pg_dump changes.

On it.

Apologies for the delay. I thought I had posted this. I rebased it against a630ac5c2016e52 (current HEAD).
Attachment

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: pg_plan_advice: rtekind uninitialized compilation waning
Next
From: Vinod Sridharan
Date:
Subject: Add a check for interrupts in ginInsert