Re: [PATCH] Extending FK check skipping on replicas to ADD FK and TRUNCATE

From: Andres Freund <andres(at)anarazel(dot)de>
To: Hannu Krosing <hannuk(at)google(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Extending FK check skipping on replicas to ADD FK and TRUNCATE
Date: 2026-08-06 13:36:23
Message-ID: ixsq2fdsdnuy5cz4yjmskjsfafwbrotawkb5qsdksmcovhtyz6@ycprtf6lcolx
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-08-06 15:17:15 +0200, Hannu Krosing wrote:
> Hi Álvaro,
>
> Can you take a look at this?
>
> This is the one I mentioned to you at the PgConf.dev, allowing the
> extension of FK check bypassing from the current "don't check on DML"
> to also include TRUNCATE and ADD FOREIGN KEY.
>
> This will especially improve replica setup cases where you would want
> to create the PK index and Foreign Keys after the initial copy. This
> speeds up the copy in extreme cases where the index presence slows
> down the initial data transfer.

You have been around long enough that this kind of reply style (at the top,
leaving everything below) is not considered ok. Yet you consistently do it.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2026-08-06 13:47:29 Re: BUG: ReadStream look-ahead exhausts local buffers when effective_io_concurrency>=64
Previous Message Hannu Krosing 2026-08-06 13:17:15 Re: [PATCH] Extending FK check skipping on replicas to ADD FK and TRUNCATE