Messages by Thread
-
-
Slow query and wrong row estimates for CTE
Dane Foster
-
Understanding logical replication lag
Patrick Molgaard
-
RE: Need information on how MM frees up disk space (vaccum) after scheduled DB cleanup by BGwCronScript/BGwLogCleaner
M Tarkeshwar Rao
-
How to deal with analyze gathering irrelevant stats
Rémi Chatenay
-
High COMMIT times
Don Seiler
-
Slow recursive CTE query questions, with row estimate and n_distinct issues
Christopher Baines
-
Conundrum with scaling out of bottleneck with hot standby, PgPool-II, etc.
Gunther Schadow
-
Reversing NULLS in ORDER causes index not to be used?
Ken Tanzer
-
Oracle to postgresql
bangalore umesh
-
RE: Autovacuum not functioning for large tables but it is working for few other small tables.
M Tarkeshwar Rao
-
Performance issues with composite types (partitioned table)
Sebastijan Wieser
-
"Required checkpoints occurs too frequently"
Atul Kumar
-
PostgeSQL JSONB Column with various type of data
Riswana Rahman
-
Index for range queries on JSON (user defined fields)
Marco Colli
-
Re: Pg_locks and pg_stat_activity
Kyotaro Horiguchi
-
Temporarily disable not null constraints
Nagaraj Raj
-
time taking deletion on large tables
Atul Kumar
-
Simple update query is slow
Nandakumar M
-
Install clustered postgres
Nunzia Vairo
-
Postgres using nested loops despite setting enable_nestloop to false
Frits Jalvingh
-
How to prioritise walsender reading from pg_wal over WAL writes?
Alexey Bashtanov
-
Low cost query - running longer
Koteswara Rao Daliparthi
-
Adding nextval() to a select caused hang/very slow execution
Eric Raskin
-
Partition pruning with joins
Ehrenreich, Sigrid
-
query plan using partial index expects a much larger number of rows than is possible
Olivier Poquet
-
Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Ehrenreich, Sigrid
-
Re: Postgres Optimizer ignores information about foreign key relationship, severely misestimating number of returned rows in join
Justin Pryzby
-
Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
David Rowley
-
Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Tom Lane
-
RE: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Ehrenreich, Sigrid
-
Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Tom Lane
-
RE: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Ehrenreich, Sigrid
-
Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Magnus Hagander
-
RE: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join
Ehrenreich, Sigrid
-
Understanding bad estimate (related to FKs?)
Philip Semanchuk
-
Profiling tool for postgresql queries
Debajyoti Datta
-
Query performance
Nagaraj Raj
-
Query Performance / Planner estimate off
Mats Julian Olsen
-
CPU Consuming query. Sequential scan despite indexing.
aditya desai