Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
| От | Nathan Bossart |
|---|---|
| Тема | Re: Add starelid, attnum to pg_stats and leverage this in pg_dump |
| Дата | |
| Msg-id | abBIu0lYyFYAq5fx@nathan обсуждение исходный текст |
| Ответ на | Re: Add starelid, attnum to pg_stats and leverage this in pg_dump (Corey Huinker <corey.huinker@gmail.com>) |
| Ответы |
Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
|
| Список | pgsql-hackers |
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. * 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. * 0003: Associated pg_dump changes. -- nathan
В списке pgsql-hackers по дате отправления: