Re: Adding REPACK [concurrently]
| От | Antonin Houska |
|---|---|
| Тема | Re: Adding REPACK [concurrently] |
| Дата | |
| Msg-id | 193349.1775046681@localhost обсуждение исходный текст |
| Ответ на | Re: Adding REPACK [concurrently] (Amit Kapila <amit.kapila16@gmail.com>) |
| Список | pgsql-hackers |
Amit Kapila <amit.kapila16@gmail.com> wrote: > On Wed, Apr 1, 2026 at 3:13 PM Antonin Houska <ah@cybertec.at> wrote: > > > > Nevertheless, I'm not sure it's a good idea for snapbuild.c to handle special > > cases like REPACK. Instead, I'm thinking if snapbuild.c can safely ignore XIDs > > of backends connected to databases other than the one we're decoding. > > > > What if such transactions have made changes in the global catalog? > Even if that won't matter, I feel such a change would be quite > fundamental to snapbuild machinery and changing at this point would be > risky. I had thought that catalog is usually needed only to retrieve the tuple descriptor, but regression tests with some Assert() statements prove now that shared catalogs can be accessed too. So that idea does not seem to be useful. -- Antonin Houska Web: https://www.cybertec-postgresql.com
В списке pgsql-hackers по дате отправления: