Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
| От | David Rowley |
|---|---|
| Тема | Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables. |
| Дата | |
| Msg-id | CAApHDvp-BsfUne0TckE5f8-E9Ou3+2+fT0aN2OB+ccC88zy-yQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables. (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
|
| Список | pgsql-bugs |
On Thu, 16 Oct 2025 at 12:36, Tom Lane <tgl@sss.pgh.pa.us> wrote: > (Hmm ... but on the third hand, if we only need one of the > two strings, couldn't we mechanize that by wrapping the > pg_get_indexdef call in CASE WHEN c.contype IS DISTINCT FROM 'x' > ?) Unless I'm mistaken, it looks like the "indexdef" field is used only when there's no corresponding constraint with contype 'p,', 'u' or 'x'. Wouldn't it be more like: CASE WHEN c.conrelid IS NULL THEN pg_catalog.pg_get_indexdef(i.indexrelid) ELSE '' END AS indexdef which saves calling the function a bit more often than what you said... ? The code I'm looking at is: /* Plain secondary index */ indxinfo[j].indexconstraint = 0; and "if (!is_constraint)" in dumpIndex(). David
В списке pgsql-bugs по дате отправления: