Re: pgsql: Fix fetching default toast value during decoding of in-progress
От | Amit Kapila |
---|---|
Тема | Re: pgsql: Fix fetching default toast value during decoding of in-progress |
Дата | |
Msg-id | CAA4eK1JUiLwmLyw99JNXrr1-9yqJULCjXbiWP2LJue96vQvWcQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Fix fetching default toast value during decoding of in-progress (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: pgsql: Fix fetching default toast value during decoding of in-progress
|
Список | pgsql-committers |
On Mon, Oct 7, 2024 at 4:16 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Mon, Oct 7, 2024 at 4:14 PM Daniel Gustafsson <daniel@yesql.se> wrote: > > > > > On 7 Oct 2024, at 12:22, Amit Kapila <akapila@postgresql.org> wrote: > > > > > > Fix fetching default toast value during decoding of in-progress transactions. > > > > v14&v15 on adder seems a bit unhappy in the test_decoding test suite: > > > > oops, will check. > I think the reason for the instability of the test in 14 and 15 is that we don't have a predictable way to start streaming in those branches. We rely on the size of the reorder buffer. This can vary based on some background activity autoanalyze or others which can generate WAL records. So, will think some more on it tomorrow on how to make it reliable in those two branches. For other branches, we used GUC debug_logical_replication_streaming to control the streaming behavior. -- With Regards, Amit Kapila.
В списке pgsql-committers по дате отправления: