Re: pgsql: Implement pg_wal_replay_wait() stored procedure - Mailing list pgsql-committers

From Alexander Korotkov
Subject Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Date
Msg-id CAPpHfduQPYWATA2rfbYXsXM+Yspn1nQVwrEs=p303O428J57Yg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Implement pg_wal_replay_wait() stored procedure  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-committers
On Fri, Aug 30, 2024 at 10:42 PM Peter Eisentraut <peter@eisentraut.org> wrote:
> On 02.08.24 20:22, Alexander Korotkov wrote:
> > Implement pg_wal_replay_wait() stored procedure
>
> Why is this under src/backend/command/?  Wouldn't it belong under
> src/backend/utils/adt/?

This path hasn't changes since the patch revision when it was a
utility command.  I agree that this doesn't look like proper path for
stored procedure.  But I don't think src/backend/utils/adt is
appropriate path either, because it's not really about data type.
pg_wal_replay_wait() looks a good neighbor for
pg_wal_replay_pause()/pg_wal_replay_resume() and other WAL-related
functions.  So, what about moving it to src/backend/access/transam?

------
Regards,
Alexander Korotkov
Supabase



pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: pgsql: Fix unfairness in all-cached parallel seq scan.
Next
From: Michael Paquier
Date:
Subject: pgsql: Rename enum labels of PG_Locale_Strategy