Re: Creating many tables gets logical replication stuck - Mailing list pgsql-general

From Keisuke Kuroda
Subject Re: Creating many tables gets logical replication stuck
Date
Msg-id CANDwggLNfkU8mQgJ1RPrQb8JQJhCvuxZ-yXo=+4u3tqperNyGA@mail.gmail.com
Whole thread Raw
In response to Re: Creating many tables gets logical replication stuck  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
Responses Re: Creating many tables gets logical replication stuck  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
List pgsql-general
Hi All,

There was a similar problem in this discussion:
  Logical decoding CPU-bound w/ large number of tables

https://www.postgresql.org/message-id/flat/CAHoiPjzea6N0zuCi%3D%2Bf9v_j94nfsy6y8SU7-%3Dbp4%3D7qw6_i%3DRg%40mail.gmail.com

> RelfilenodeMapHash from 1024 entries to 64.
The above changes reduced the performance impact.

However, I think the problem that there are too
many invalidations of RelfilenodeMapHash still remains.
As you report, when many tables are created/dropped/truncated,
The walsender process can get stuck.

-- 
Keisuke Kuroda
NTT Software Innovation Center
keisuke.kuroda.3862@gmail.com



pgsql-general by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: Row estimates for empty tables
Next
From: Dirk Lattermann
Date:
Subject: Trigger transaction isolation