Re: PgSQL 15.3: Execution plan not using index as expected

Thanks Rob,

no it's not a problem with the index. It's a problem with the use of
CURRENT_USER in the WHERE
I submitted a new post on this matter with a test case.

Kind regards

======================================
Dürr Software Entw.
Guggenberg 26, DE-82380 Peißenberg
fon: +49-8803-4899016 fax: +49-8803-4899017
info(at)fduerr(dot)de

Am 12.08.23 um 04:25 schrieb rob stone:
> Hello,
>
>> ---------------------------------------------------------------------
>> -------------------------
>>   PostgreSQL 9.3.4 on x86_64-unknown-linux-gnu, compiled by gcc
>> (Debian
>> 4.8.3-2) 4.8.3, 64-bit
>>
>>
>> ---------------------------------------------------------------------
>> ------------------------------------------------
>>   PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu,
>> compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
>> (1 Zeile)
>>
>>
> 9.3 plan
> -> Index Scan using client_session_user_id_idx on client_session
>
> Looks like a collation issue given the difference in compilers used.
> In the 9.3 plan the index is used.
> Maybe try a reindex of the table.
>
> HTH,
> Rob
>