| From: | David Barbour <david(dot)barbour(at)amiralearning(dot)com> |
|---|---|
| To: | Jon Zeppieri <zeppieri(at)gmail(dot)com> |
| Cc: | Igor Korot <ikorot01(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Get info about the index |
| Date: | 2025-07-28 13:19:56 |
| Message-ID: | CAEMHB2QQpfxjbqbyB6zy+TMv9zf42tavLuYUSxDXgyZEaq46Xg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Couple of suggestions. You might try ChatGPT. I've had some success using
this tool to uncover improvements to the use of indexes. The other would
be to look at https://explain.depesz.com/. It's pretty self-explanatory.
You run an explain plan and paste the results into the tool and it will run
an automated analysis.
On Sat, Jul 26, 2025 at 2:51 PM Jon Zeppieri <zeppieri(at)gmail(dot)com> wrote:
> On Sat, Jul 26, 2025 at 3:13 PM Igor Korot <ikorot01(at)gmail(dot)com> wrote:
> >
> > I didn't find the sorting for the field.
> >
> > Can you help?
>
> The pg_index_column_has_property() can provide this information. E.g.,
>
> select pg_index_column_has_property('my_index'::regclass, 2, 'desc');
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-07-28 15:13:18 | Re: Get info about the index |
| Previous Message | DINESH NAIR | 2025-07-28 06:06:54 | Re: Regarding logical replication issues with PostgreSQL versions 16 and above |