| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | bossartn(at)amazon(dot)com, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, michael(at)paquier(dot)xyz, sulamul(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: inefficient loop in StandbyReleaseLockList() |
| Date: | 2021-11-06 23:13:31 |
| Message-ID: | 641260.1636240411@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-11-06 18:32:54 -0400, Tom Lane wrote:
>> Good point. The note at list_delete_last that it's O(1) isn't really
>> on point --- instead, the text for list_delete_first should be like
>>
>> + * Note that this takes time proportional to the length of the list,
>> + * since the remaining entries must be moved. Consider reversing the
>> + * list order so that you can use list_delete_last() instead. However,
>> + * if that causes you to replace lappend() with lcons(), you haven't
>> + * improved matters.
> LGTM
Done that way, then.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2021-11-07 01:31:57 | XLogReadRecord() error in XlogReadTwoPhaseData() |
| Previous Message | Andres Freund | 2021-11-06 22:46:48 | Re: inefficient loop in StandbyReleaseLockList() |