Re: improve performance of pg_dump with many sequences
| От | Nathan Bossart |
|---|---|
| Тема | Re: improve performance of pg_dump with many sequences |
| Дата | |
| Msg-id | aV7r43VN-kBR6T8v@nathan обсуждение исходный текст |
| Ответ на | Re: improve performance of pg_dump with many sequences (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: improve performance of pg_dump with many sequences
|
| Список | pgsql-hackers |
On Wed, Jan 07, 2026 at 06:13:48PM -0500, Tom Lane wrote: > Nathan Bossart <nathandbossart@gmail.com> writes: >> Before v18, pg_dump just ERRORs due to insufficient privileges on a >> sequence. IMHO that makes sense. If you ask pg_dump to dump something you >> don't have privileges on, I'd expect it to error instead of silently >> skipping it. > > That would be a fine argument were it not that collectSequences() > tries to vacuum up the data for every sequence in the DB, whether > the user has asked to dump them all or not. In other places in > pg_dump, we avoid such problems by restricting which tables we > ask for data about ... but not here. I meant that we could teach pg_dump to error in dumpSequenceData() if it sees nulls for the sequence in question. -- nathan
В списке pgsql-hackers по дате отправления: