Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
| От | Amit Kapila |
|---|---|
| Тема | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher |
| Дата | |
| Msg-id | CAA4eK1+0zu9dCTCTSh92rLYtGY_B6EkGWzDAn9+SK2DHGodHgA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher (Önder Kalacı <onderkalaci@gmail.com>) |
| Ответы |
Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
|
| Список | pgsql-hackers |
On Mon, Mar 13, 2023 at 6:14 PM Önder Kalacı <onderkalaci@gmail.com> wrote: > >> >> >> 3. Removed the cases for dropping the index. This ensures that after >> dropping the index on the table we switch to either an index scan (if >> a new index is created) or to a sequence scan. It doesn't seem like a >> very interesting case to me. > > > For that test, my goal was to ensure/show that the invalidation callback > is triggered after `DROP / CREATE INDEX` commands. > Fair point. I suggest in that case just keep one of the tests for Drop Index such that after that it will pick up a sequence scan. However, just do the poll for the number of index scans stat once. I think that will cover the case you are worried about without having a noticeable impact on test timing. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: