Re: LwLocks contention

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: LwLocks contention
Дата
Msg-id CAMcsB=ydc_FGbn1UwRqboGCfx1mZAAYBgphiC6gtv3qHiVXCBg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: LwLocks contention  (Chris Bisnett <cbisnett@gmail.com>)
Ответы Re: LwLocks contention  (Robert Treat <rob@xzilla.net>)
Список pgsql-general
On Thu, Apr 21, 2022 at 6:17 AM Chris Bisnett <cbisnett@gmail.com> wrote:
We're working to update our application so that we can
take advantage of the pruning. Are you also using native partitioning?

No partitioned tables at all, but we do have 1800 tables and some very complex functions, some trigger insanity, huge number of indexes, etc etc.

There are lots of things to fix, but I just do not yet have a good sense of the most important thing to address right now to reduce the odds of this type of traffic jam occurring again. I very much appreciate you sharing your experience. If I could reliably reproduce the issue or knew what data points to start collecting going forward, that would at least give me something to go on, but it feels like I am just waiting for it to happen again and hope that some bit of information makes itself known that time.

Perhaps I should have posted this to the performance list instead of general. 

В списке pgsql-general по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: Huge archive log generate in Postgresql-13
Следующее
От: Radoslav Nedyalkov
Дата:
Сообщение: set column statistics to max does not help