Postgres version: PostgreSQL 11.18, compiled by Visual C++ build 1800, 64-bit relname |relpages|reltuples|relallvisible|relkind|relnatts|relhassubclass|reloptions|pg_table_size| ---------------------+--------+---------+-------------+-------+--------+--------------+----------+-------------+ store_seller_products|16007942|843460096| 797033|r | 16|false |NULL | 131980795904|
relname |relpages|reltuples|relallvisible|relkind|relnatts|relhassubclass|reloptions|pg_table_size| ------------------------+--------+---------+-------------+-------+--------+--------------+----------+-------------+ products_inventory_delta| 2847202|259351648| 1606201|r | 4|false |NULL | 23330758656| Peak load (write): 3000 TPS (mostly updates). Peak load (read): 800 TPS. On Sat, Mar 9, 2024 at 5:58 PM Ron Johnson <ronljohnso...@gmail.com> wrote: > On Sat, Mar 9, 2024 at 7:18 AM hassan rafi <haassaan.kh...@gmail.com> > wrote: > >> Hi team, >> >> We are seeing unusually high query planning times on our Postgres server. >> I am attaching a few query plans. >> > > Postgresql version number? > Rows in the tables? > System load? >
