Re: [HACKERS] make async slave to wait for lsn to be replayed

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Kartyshov Ivan <i(dot)kartyshov(at)postgrespro(dot)ru>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, dilipbalaut(at)gmail(dot)com, smithpb2250(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed
Date: 2024-03-28 07:36:32
Message-ID: CA+hUKGKXXP8ZgTfFfjhv77ALC-ZKcejR4pdfrfgVqYrG_75zeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> v12

Hi all,

I didn't review the patch but one thing jumped out: I don't think it's
OK to hold a spinlock while (1) looping over an array of backends and
(2) making system calls (SetLatch()).

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2024-03-28 08:13:46 Re: Add new error_action COPY ON_ERROR "log"
Previous Message Masahiko Sawada 2024-03-28 07:34:36 Re: Improve tab completion for ALTER DEFAULT PRIVILEGE and ALTER TABLE