Dear Marc,
Thanks for the reply!
> Thanks for your suggestions that were both already tested. In our (real) case (a
> single transaction with 12 millions sub-transactions):
>
> 1) setting the subscription as streaming, just delay a bit the spill file surge. It does
> not prevent the creation of spill files.
It is bit surprised for me because I don't know the path which transactions can
be serialized even in the streaming=on case. Let me think over it...
> 2) we set logical_decoding_work_mem to 20GB, which probably also delayed the
> problem, but did not solve it.
Oh, I understood that you've already increased the parameter to the appropriate
value on your env. Is it right?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
