Re: inefficient loop in StandbyReleaseLockList() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: inefficient loop in StandbyReleaseLockList()
Date
Msg-id 364794.1636071716@sss.pgh.pa.us
Whole thread Raw
In response to Re: inefficient loop in StandbyReleaseLockList()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: inefficient loop in StandbyReleaseLockList()
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I wonder if it's worth adding a note to list_delete_first() mentioning its
> O(N) behaviour. It's not immediately visible from the code, and from the list
> name one could very well be excused to not be worried about O(N) costs.

Hm.  I think it's not the only list function with O(N) behavior;
in fact there used to be more such functions than there are now.
But I could get behind a patch that annotates all of them.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Fix WAL replay in presence of an incomplete record
Next
From: Tomas Vondra
Date:
Subject: Re: [sqlsmith] Failed assertion in brin_minmax_multi_distance_float4 on REL_14_STABLE