| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Ramakrishna m <ram(dot)pgdb(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, ravisql09(at)gmail(dot)com |
| Subject: | Re: Logical Replication Delay |
| Date: | 2024-09-25 14:42:07 |
| Message-ID: | CAKAnmmLmvuo=TORx=hDw2y5fFOUc0sHb88O+6Z-Cs=oVtN9W4A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Sep 21, 2024 at 3:08 PM Ramakrishna m <ram(dot)pgdb(at)gmail(dot)com> wrote:
> I would greatly appreciate any suggestions you may have to help avoid
> logical replication delays, whether through tuning database or operating
> system parameters, or any other recommendations
>
In addition to the things already answered:
* What is the use case for logical replication? I assume your local
replicas are able to keep up just fine.
* Check the nature of the work for problems, e.g. ORM doing
unnecessary/redundant updates, maintaining indexes that are not really
needed
* Looks like your wal_segment_size was boosted to 1GB. What drove that
change?
* Yes, autovacuum could affect things - make sure
log_autovacuum_min_durations is set
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-09-25 15:36:13 | Re: PgBackRest : Restore to a checkpoint shows further transactions |
| Previous Message | Laurenz Albe | 2024-09-25 10:44:23 | Re: MError after replication in postgresql |