Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Date
Msg-id CAA4eK1LgoXwwJPvEWSNGW1SbquLCRdgBuHbd3nVfOB64KeLUPA@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions  (Ajin Cherian <itsajin@gmail.com>)
Responses Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
List pgsql-hackers
On Wed, Jul 8, 2020 at 7:31 PM Ajin Cherian <itsajin@gmail.com> wrote:
>
> I was going through this thread and testing and reviewing the patches, I think this is a great feature to have and
onewhich customers would appreciate. I wanted to help out, and I saw a request for a test patch for a GUC to always
enablestreaming on logical replication. Here's one on top of patchset v31, just in case you still need it. By default
theGUC is turned on, I ran the regression tests with it and didn't see any errors. 
>

Thanks for showing the interest in patch.  How have you ensured that
streaming is happening?  I don't think the proposed patch can ensure
it for every case because we also rely on logical_decoding_work_mem to
decide whether to stream/spill, see ReorderBufferCheckMemoryLimit.  I
think with your patch it will allow streaming for cases where we have
large amount of WAL to decode.

I feel you need to add some DEBUG messages (or some other way) to
ensure that all existing and new test cases related to logical
decoding will perform the streaming.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: "movead.li@highgo.ca"
Date:
Subject: Re: A patch for get origin from commit_ts.
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: Implement UNLOGGED clause for COPY FROM