Re: speed up a logical replica setup

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>, "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: "Alexander Lakhin" <exclusion(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>
Subject: Re: speed up a logical replica setup
Date: 2024-07-30 00:05:26
Message-ID: 697d692f-f9d3-41f6-9f0e-29a4fb18e544@app.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 29, 2024, at 6:11 PM, Euler Taveira wrote:
> The options are:
>
> (a) temporary replication slot: requires an additional replication slot.
> small payload. it is extremely slow in comparison with the other
> options.
> (b) logical message: can be consumed by logical replication when/if it
> is supported some day. big payload. fast.
> (c) snapshot of running txn: small payload. fast.
> (d) named restore point: biggest payload. fast.
>
> I don't have a strong preference but if I need to pick one I would
> choose option (c) or option (d). The option (a) is out of the question.

I'm attaching a patch that implements option (c). While reading the code
I noticed that I left a comment that should be removed by commit
b9639138262. 0002 removes it.

--
Euler Taveira
EDB https://www.enterprisedb.com/

Attachment Content-Type Size
0001-pg_createsubscriber-fix-slow-recovery.patch text/x-patch 2.0 KB
0002-pg_createsubscriber-remove-obsolete-comment.patch text/x-patch 1.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2024-07-30 00:39:44 Re: Remove last traces of HPPA support
Previous Message Erik Wienhold 2024-07-29 23:36:55 Re: psql: Add leakproof field to \dAo+ meta-command results