From: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com> |
---|---|
To: | romdn(at)inbox(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16327: Too many files in pg_replslot folder |
Date: | 2020-03-29 19:52:29 |
Message-ID: | CAH503wCqBDjS+X3NRJrTaT+-HNY+4LW40rpNPctzcS1V3tVy-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, 29 Mar 2020 at 11:49, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
>
> P.S. Replication on PostgreSql 11.1 (with default settings) worked fine
> with
> inserting 4.5 million rows. The xid - * - lsn - * - *. Snap files were
> smaller and larger in size. But if there were several inserts in a row of
> 4.5 million lines, an error appeared: ERROR: out of memory.
>
> Could you provide a test case? Are you using subtransactions?
logical_decoding_work_mem [1] was added in v13 to ameliorate some high
memory usage while decoding transactions. It is weird that it does not 'out
of memory' in v11 too (v11 introduced Generational memory allocator to
reduce logical decoding memory usage); I expect a high memory usage in v10
in a big transaction scenario.
If you are looking for a workaround, you should try to disable all
subscriptions and then enable only one at a time.
Regards,
--
Euler Taveira http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2020-03-29 20:33:43 | BUG #16328: Generated column and inheritance: strange default error |
Previous Message | PG Bug reporting form | 2020-03-29 14:48:36 | BUG #16327: Too many files in pg_replslot folder |