Re: pgsql: Implement pg_wal_replay_wait() stored procedure

From: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Date: 2024-10-22 13:32:51
Message-ID: CALT9ZEHyEDx=GWffOxRm0WZD8JkMBBp+Et6TtBO1rjV8Q3UpSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Fix a typo of myself:

> Maybe refactoring for loop for assigning result variable and breaking a
> loop instead of immediate return would look better and lead to natural call
> of after the loop before returning.
>
Maybe refactoring for loop for assigning result variable and breaking a
loop instead of immediate return would look better and lead to natural call
of *deleteLSNWaiter()* after the loop before returning.

Pavel.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Álvaro Herrera 2024-10-22 14:26:01 pgsql: Restructure foreign key handling code for ATTACH/DETACH
Previous Message Pavel Borisov 2024-10-22 13:30:20 Re: pgsql: Implement pg_wal_replay_wait() stored procedure

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-10-22 13:42:41 Re: Using read_stream in index vacuum
Previous Message Pavel Borisov 2024-10-22 13:30:20 Re: pgsql: Implement pg_wal_replay_wait() stored procedure