Re: Implement waiting for wal lsn replay: reloaded - Mailing list pgsql-hackers

From Yura Sokolov
Subject Re: Implement waiting for wal lsn replay: reloaded
Date
Msg-id 15bae381-7667-4646-8068-b371a2534721@postgrespro.ru
Whole thread Raw
In response to Re: Implement waiting for wal lsn replay: reloaded  (Yura Sokolov <y.sokolov@postgrespro.ru>)
Responses Re: Implement waiting for wal lsn replay: reloaded
List pgsql-hackers
17.02.2025 00:27, Alexander Korotkov wrote:
> On Thu, Feb 6, 2025 at 10:31 AM Yura Sokolov <y.sokolov@postgrespro.ru> wrote:
>> I briefly looked into patch and have couple of minor remarks:
>>
>> 1. I don't like `palloc` in the `WaitLSNWakeup`. I believe it wont issue
>> problems, but still don't like it. I'd prefer to see local fixed array, say
>> of 16 elements, and loop around remaining function body acting in batch of
>> 16 wakeups. Doubtfully there will be more than 16 waiting clients often,
>> and even then it wont be much heavier than fetching all at once.
> 
> OK, I've refactored this to use static array of 16 size.  palloc() is
> used only if we don't fit static array.

I've rebased patch and:
- fixed compiler warning in wait.c ("maybe uninitialized 'result'").
- made a loop without call to palloc in WaitLSNWakeup. It is with "goto" to
keep indentation, perhaps `do {} while` would be better?

-------
regards
Yura Sokolov aka funny-falcon
Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.