Re: pgsql: Implement pg_wal_replay_wait() stored procedure

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Date: 2024-04-02 23:23:50
Message-ID: CA+hUKGLYvGc=6W4vS9YuE3FYe7aZp++_wHu13_aj8=j4d99Gxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Apr 3, 2024 at 9:42 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> On Tue, Apr 2, 2024 at 10:58 PM Alexander Korotkov
> <akorotkov(at)postgresql(dot)org> wrote:
> > Implement pg_wal_replay_wait() stored procedure
>
> I'm trying to figure out if this failure could be related to this commit...
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-04-02%2020%3A24%3A55

I think you might need to move WaitLSNShmemInit() down to
CreateOrAttachShmemStructs(), otherwise -DEXEC_BACKEND build dies with
a NULL pointer. (Huh, why doesn't that animal show a backtrace?)

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2024-04-02 23:24:17 Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Previous Message David Rowley 2024-04-02 22:40:57 pgsql: Don't zero tuple_fraction when planning UNIONs with ORDER BYs