pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: bad estimates
2003-08-29 03:46 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 04:05 UTC Bruno Wolff III <bruno@wolff.to>
` Re: bad estimates
2003-08-29 04:09 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 04:24 UTC Bruno Wolff III <bruno@wolff.to>
` Re: bad estimates
2003-08-29 07:01 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 07:57 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 08:10 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 08:15 UTC Christopher Kings-Lynne <chriskl@familyhealth.com.au>
` Re: bad estimates
2003-08-29 08:17 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 12:52 UTC Jeff <threshar@torgo.978.org>
` Re: bad estimates
2003-08-29 15:02 UTC Stephan Szabo <sszabo@megazone.bigpanda.com>
` Re: bad estimates
2003-08-29 16:06 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 16:36 UTC Sean Chittenden <sean@chittenden.org>
` Re: bad estimates
2003-08-29 16:56 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-29 17:03 UTC Sean Chittenden <sean@chittenden.org>
` Re: bad estimates
2003-08-30 02:55 UTC Bruno Wolff III <bruno@wolff.to>
` Re: bad estimates
2003-08-30 05:05 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-30 07:38 UTC Ken Geis <kgeis@speakeasy.org>
` Re: bad estimates
2003-08-30 14:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Bad estimates
2017-11-22 14:29 UTC =?iso-8859-2?Q?Artur_Zaj=B1c?= <azajac@ang.com.pl>
` Re: Bad estimates
2017-11-22 14:49 UTC Don Seiler <don@seiler.us>
` Re: Bad estimates
2017-11-22 15:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: Bad estimates
2017-11-22 15:05 UTC Alex Ignatov <a.ignatov@postgrespro.ru>
` Re: Bad estimates
2017-11-22 15:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Bad estimates
2017-11-22 16:52 UTC =?iso-8859-2?Q?Artur_Zaj=B1c?= <azajac@ang.com.pl>
[25+ messages in thread]
Re: Bad estimates (DEFAULT_UNK_SEL)
2017-11-22 14:57 UTC Justin Pryzby <pryzby@telsasoft.com>
Using GROUPING SETS with more than one set disables predicate pushdown?
2017-11-21 11:04 UTC Zakhar Shapurau <zak@zvs.no>
` Re: Using GROUPING SETS with more than one set disables predicate pushdown?
2017-11-21 14:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Using GROUPING SETS with more than one set disables predicate pushdown?
2017-11-21 18:16 UTC Andres Freund <andres@anarazel.de>
[3+ messages in thread]
POWA doesn't show queries executed
2017-11-18 01:52 UTC Neto pr <netopr9@gmail.com>
` Re: [PERFORM] POWA doesn't show queries executed
2017-11-21 08:00 UTC phb07 <phb07@apra.asso.fr>
` Re: [PERFORM] POWA doesn't show queries executed
2017-11-21 15:29 UTC Marco Nietz <pg@mnietz.de>
[3+ messages in thread]
Migration to pglister - Before
2017-11-20 14:33 UTC Stephen Frost <sfrost@snowman.net>
` Re: [ADMIN] Migration to pglister - Before
2017-11-20 15:30 UTC Achilleas Mantzios <achill@matrix.gatewaynet.com>
` Re: [ADMIN] Migration to pglister - Before
2017-11-20 15:34 UTC Stephen Frost <sfrost@snowman.net>
[3+ messages in thread]
Migration to PGLister - After
2017-11-20 15:03 UTC Stephen Frost <sfrost@snowman.net>
PostgreSQL 9.6 wals management
2017-11-20 09:02 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: PostgreSQL 9.6 wals management
2017-11-20 12:28 UTC Michael Paquier <michael.paquier@gmail.com>
` Re: PostgreSQL 9.6 wals management
2017-11-20 12:56 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
[3+ messages in thread]
CREATE STATISTICS and join selectivity
2017-11-15 20:19 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: CREATE STATISTICS and join selectivity
2017-11-15 23:47 UTC David Rowley <david.rowley@2ndquadrant.com>
[2+ messages in thread]
Query planner gaining the ability to replanning after start of query execution.
2017-11-13 16:44 UTC Oliver Mattos <omattos@gmail.com>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-13 20:06 UTC Arne Roland <A.Roland@index.de>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-13 21:51 UTC Oliver Mattos <omattos@gmail.com>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-13 22:48 UTC Arne Roland <A.Roland@index.de>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-13 22:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-13 23:20 UTC Oliver Mattos <omattos@gmail.com>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-14 21:26 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: Query planner gaining the ability to replanning after start of query execution.
2017-11-15 19:57 UTC Gunter <raj@gusw.net>
[8+ messages in thread]
DB slowness after upgrade from Postgres 9.1 to 9.4
2017-11-10 10:58 UTC p kirti <kirtip92@gmail.com>
` Re: DB slowness after upgrade from Postgres 9.1 to 9.4
2017-11-12 19:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
overestimate on empty table
2017-11-10 20:40 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: overestimate on empty table
2017-11-10 21:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: overestimate on empty table
2017-11-11 17:19 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: overestimate on empty table
2017-11-11 17:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Performance loss upgrading from 9.3 to 9.6
2017-11-06 13:18 UTC Adam Torres <atorres@amplify-nation.com>
` Re: Performance loss upgrading from 9.3 to 9.6
2017-11-06 14:21 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Performance loss upgrading from 9.3 to 9.6
2017-11-06 21:12 UTC Adam Torres <atorres@amplify-nation.com>
` Re: Performance loss upgrading from 9.3 to 9.6
2017-11-07 02:59 UTC Adam Brusselback <adambrusselback@gmail.com>
` Re: Performance loss upgrading from 9.3 to 9.6
2017-11-07 05:11 UTC Justin Pryzby <pryzby@telsasoft.com>
[5+ messages in thread]
Dynamic performance issues
2017-11-06 20:05 UTC Arne Roland <A.Roland@index.de>
Index-Advisor Tools
2017-10-31 17:12 UTC Neto pr <netopr9@gmail.com>
` Re: Index-Advisor Tools
2017-10-31 17:19 UTC Anthony Sotolongo <asotolongo@gmail.com>
` Re: Index-Advisor Tools
2017-10-31 17:25 UTC Neto pr <netopr9@gmail.com>
` Re: Index-Advisor Tools
2017-10-31 19:25 UTC Alexandre de Arruda Paes <adaldeia@gmail.com>
` Re: Index-Advisor Tools
2017-10-31 20:04 UTC Yves Dorfsman <yves@zioup.com>
` Re: Index-Advisor Tools
2017-10-31 20:04 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Index-Advisor Tools
2017-11-06 18:52 UTC Baron Schwartz <baron.schwartz@gmail.com>
[7+ messages in thread]
Unnecessary DISTINCT while primary key in SQL
2017-11-04 15:20 UTC 刘瑞 <whx20202@gmail.com>
` Re: Unnecessary DISTINCT while primary key in SQL
2017-11-06 00:34 UTC David Rowley <david.rowley@2ndquadrant.com>
[2+ messages in thread]
OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-02 00:28 UTC Gunther <raj@gusw.net>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-02 02:44 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-02 08:30 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-02 16:36 UTC Gunther <raj@gusw.net>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-02 17:14 UTC Gunther <raj@gusw.net>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-02 18:03 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 08:01 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 09:28 UTC Thomas Kellerer <spam_eater@gmx.net>
` Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 12:07 UTC Adam Brusselback <adambrusselback@gmail.com>
` Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 14:36 UTC Gunther <raj@gusw.net>
` Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 14:51 UTC Gunther <raj@gusw.net>
` Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 14:55 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 15:13 UTC Gunther <raj@gusw.net>
` Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
2017-11-03 15:56 UTC Dave Nicponski <dave@seamlessdocs.com>
[14+ messages in thread]
Cursor vs Set Operation
2017-10-30 22:51 UTC patibandlakoshal <patibandlakoshal@gmail.com>
` Re: Cursor vs Set Operation
2017-11-01 16:28 UTC Merlin Moncure <mmoncure@gmail.com>
[2+ messages in thread]
Massive insert vs heavy contention in LWLock:buffer_content
2017-10-31 16:30 UTC luisfpg <lfpg.dev@gmail.com>
[PATCH 1/3] Provide overflow safe integer math inline functions.
2017-10-30 05:13 UTC Andres Freund <andres@anarazel.de>
Cheaper subquery scan not considered unless offset 0
2017-10-29 11:24 UTC Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Cheaper subquery scan not considered unless offset 0
2017-10-29 11:46 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: Cheaper subquery scan not considered unless offset 0
2017-10-29 13:17 UTC Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Cheaper subquery scan not considered unless offset 0
2017-10-29 14:41 UTC Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Cheaper subquery scan not considered unless offset 0
2017-10-29 14:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
WAL still kept in pg_xlog even long after heavy workload is done
2017-10-27 11:28 UTC Stefan Petrea <Stefan.Petrea@tangoe.com>
` Re: WAL still kept in pg_xlog even long after heavy workload is done
2017-10-27 12:50 UTC MichaelDBA <MichaelDBA@sqlexec.com>
[2+ messages in thread]
postgresql tuning with perf
2017-10-23 19:19 UTC Purav Chovatia <puravc@gmail.com>
` Re: postgresql tuning with perf
2017-10-23 20:29 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: postgresql tuning with perf
2017-10-23 20:55 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: postgresql tuning with perf
2017-10-23 21:59 UTC Steve Atkins <steve@blighty.com>
` Re: postgresql tuning with perf
2017-10-24 07:36 UTC Purav Chovatia <puravc@gmail.com>
` Re: postgresql tuning with perf
2017-10-24 11:33 UTC Purav Chovatia <puravc@gmail.com>
` Re: postgresql tuning with perf
2017-10-24 11:39 UTC Purav Chovatia <puravc@gmail.com>
` Re: postgresql tuning with perf
2017-10-24 14:51 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: postgresql tuning with perf
2017-10-24 15:06 UTC Purav Chovatia <puravc@gmail.com>
` Re: postgresql tuning with perf
2017-10-24 15:08 UTC Purav Chovatia <puravc@gmail.com>
` Re: postgresql tuning with perf
2017-10-24 15:21 UTC legrand legrand <legrand_legrand@hotmail.com>
[11+ messages in thread]
Row-level security performance
2017-10-24 02:51 UTC Jason Borg <jasonb@sunpay.com.au>
Low priority batch insert
2017-10-19 16:10 UTC Jean Baro <jfbaro@gmail.com>
` Re: Low priority batch insert
2017-10-19 22:54 UTC Michael Paquier <michael.paquier@gmail.com>
[2+ messages in thread]
memory allocation
2004-06-18 13:34 UTC Michael Ryan S. Puncia <mpuncia@census.gov.ph>
` Re: memory allocation
2004-06-18 13:39 UTC Devrim GUNDUZ <devrim@gunduz.org>
` Re: memory allocation
2004-06-18 13:58 UTC Richard Huxton <dev@archonet.com>
` Memory Allocation
2008-11-26 22:09 UTC Ryan Hansen <ryan.hansen@brightbuilders.com>
` Re: Memory Allocation
2008-11-26 22:18 UTC Alan Hodgson <ahodgson@simkin.ca>
` Re: Memory Allocation
2008-11-26 22:47 UTC Carlos Moreno <morenopg@mochima.com>
` Re: Memory Allocation
2008-11-26 22:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory Allocation
2008-11-26 23:00 UTC Scott Carey <scott@richrelevance.com>
` Re: Memory Allocation
2008-11-26 23:09 UTC Kevin Grittner <Kevin.Grittner@wicourts.gov>
` Re: Memory Allocation
2008-11-26 23:52 UTC Scott Carey <scott@richrelevance.com>
` Re: Memory Allocation
2008-11-28 22:28 UTC Kevin Grittner <Kevin.Grittner@wicourts.gov>
` memory allocation
2017-10-17 09:28 UTC nijam J <nijamutheenblogs1@gmail.com>
` Re: memory allocation
2017-10-19 12:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[13+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox