Re: Adding REPACK [concurrently]
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Adding REPACK [concurrently] |
| Дата | |
| Msg-id | aeZG8QZKMDGdcnK_@alvherre.pgsql обсуждение |
| Ответ на | Re: Adding REPACK [concurrently] (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: Adding REPACK [concurrently]
|
| Список | pgsql-hackers |
On 2026-Apr-20, Alvaro Herrera wrote: > On 2026-Apr-20, Tom Lane wrote: > > I think you need to move these tests out into some other test suite > > (or make a new one). > > I'll see what I can find. I think the simplest would be to add them to src/test/modules/injection_points. We already have some repack tests there (because they needed injection points), and it has an SQL suite, so we would not be adding any extra overhead. However, the new tests are not related to injection points, so they would be out of place. Another possibility could be src/test/subscription, but it doesn't have sql tests; doesn't seem good to have them just for this. There's also contrib/test_decoding. It's somewhat vaguely adjacent, and the tests aren't _really_ about the decoding part, but of all these options, it seems the least bad one. I don't like the idea of adding another suite. Too much scaffolding for so little, I think. I don't have any other ideas ATM. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "We're here to devour each other alive" (Hobbes)
В списке pgsql-hackers по дате отправления: