| From: | rob stone <floriparob(at)tpg(dot)com(dot)au> |
|---|---|
| To: | Dürr Software <info(at)fduerr(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PgSQL 15.3: Execution plan not using index as expected |
| Date: | 2023-08-12 02:25:36 |
| Message-ID: | f91820f43eb45bab7e9d93b994a00985d9a28285.camel@tpg.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2023-08-12 08:17:08 | Re: How to set default privilege for new users to have no access to other databases? |
| Previous Message | Adrian Klaver | 2023-08-11 14:32:31 | Re: PgSQL 15.3: Execution plan not using index as expected |