Search Postgresql Archives

Re: How should we design our tables and indexes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: How should we design our tables and indexes
From: Greg Sabino Mullane <htamfids@xxxxxxxxx>
Date: Mon, 12 Feb 2024 14:12:36 -0500
Cc: pgsql-general <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAB+=1TWM2Pwg3ReD7qsGQNpPGyNwo+4m1SS_eMbt63ai=qbMOg@mail.gmail.com>
References: <CAB+=1TXnsSW384gsJxOFvzJt=+coUWh5my39mkHwZEEWPFCsWQ@mail.gmail.com> <CAKAnmmL=x_3Ga_aBa1UQfHjcCikV7SJX5iM9n4b0bb76cgZVyQ@mail.gmail.com> <CAB+=1TV=bAokrJhM9JjqfLTpemyr3SwbJLTFpXmfggtcw2qKCg@mail.gmail.com> <CAKAnmmLt68Tgza-mL-cJS1=-13PO6vjfbNUCgBfJwU_030=fxA@mail.gmail.com> <CAB+=1TWM2Pwg3ReD7qsGQNpPGyNwo+4m1SS_eMbt63ai=qbMOg@mail.gmail.com>

> Is there any way to track those historical executions and be able to find the exact root cause of the slow executions confidently?

https://www.postgresql.org/docs/current/auto-explain.html

auto_explain.log_min_duration = '5s' ## or large enough to capture your quickest one

Do NOT enable auto_explain.log_analyze.

Cheers,

Greg

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- How should we design our tables and indexes
  - From: veem v
- Re: How should we design our tables and indexes
  - From: Greg Sabino Mullane
- Re: How should we design our tables and indexes
  - From: veem v
- Re: How should we design our tables and indexes
  - From: Greg Sabino Mullane
- Re: How should we design our tables and indexes
  - From: veem v

Prev by Date: Re: How should we design our tables and indexes
Next by Date: Re: How to do faster DML
Previous by thread: Re: How should we design our tables and indexes
Next by thread: Re: How should we design our tables and indexes
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]