Re: Creating many tables gets logical replication stuck

From: Keisuke Kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Creating many tables gets logical replication stuck
Date: 2020-08-25 06:50:17
Message-ID: CANDwggLNfkU8mQgJ1RPrQb8JQJhCvuxZ-yXo=+4u3tqperNyGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)kuroda(dot)3862(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2020-08-25 07:32:42 Re: Row estimates for empty tables
Previous Message Justin Pryzby 2020-08-25 00:06:25 Re: Row estimates for empty tables