pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedHow to log quires which are taking time in PostgreSQL 9.1.
2017-02-23 16:21 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: How to log quires which are taking time in PostgreSQL 9.1.
2017-02-23 16:30 UTC ProPAAS DBA <dba@propaas.com>
` Re: How to log quires which are taking time in PostgreSQL 9.1.
2017-02-23 16:44 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: How to log quires which are taking time in PostgreSQL 9.1.
2017-02-23 16:59 UTC Luis Fernando Simone <luis.simone@datacoper.com.br>
` Re: How to log quires which are taking time in PostgreSQL 9.1.
2017-02-23 17:21 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
[5+ messages in thread]
Query performance changes significantly depending on limit value
2017-02-23 13:11 UTC Rowan Seymour <rowanseymour@gmail.com>
` Re: Query performance changes significantly depending on limit value
2017-02-23 13:32 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Query performance changes significantly depending on limit value
2017-02-23 14:02 UTC Rowan Seymour <rowanseymour@gmail.com>
` Re: Query performance changes significantly depending on limit value
2017-02-23 15:35 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Query performance changes significantly depending on limit value
2017-02-23 16:45 UTC Rowan Seymour <rowanseymour@gmail.com>
` Re: Query performance changes significantly depending on limit value
2017-02-23 17:13 UTC Pavel Stehule <pavel.stehule@gmail.com>
[6+ messages in thread]
Correct use of cursors for very large result sets in Postgres
2017-02-17 07:59 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-17 12:04 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-17 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-18 07:57 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-18 08:46 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-18 17:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-19 07:54 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-21 12:36 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-21 13:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-21 13:49 UTC Mike Beaton <mjsbeaton@gmail.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-21 14:06 UTC John Gorman <jgorman@eldocomp.com>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-23 03:13 UTC Vitalii Tymchyshyn <vit@tym.im>
` Re: Correct use of cursors for very large result sets in Postgres
2017-02-23 12:47 UTC John Gorman <jgorman@eldocomp.com>
[13+ messages in thread]
Number of characters in column preventing index usage
2017-02-17 22:19 UTC Hustler DBA <hustlerdba@gmail.com>
` Re: Number of characters in column preventing index usage
2017-02-17 22:42 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Number of characters in column preventing index usage
2017-02-17 22:49 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Number of characters in column preventing index usage
2017-02-17 22:51 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Number of characters in column preventing index usage
2017-02-17 22:52 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Number of characters in column preventing index usage
2017-02-17 23:16 UTC Hustler DBA <hustlerdba@gmail.com>
` Re: Number of characters in column preventing index usage
2017-02-17 23:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Number of characters in column preventing index usage
2017-02-18 00:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Number of characters in column preventing index usage
2017-02-18 00:16 UTC Hustler DBA <hustlerdba@gmail.com>
[9+ messages in thread]
pgsql connection timeone
2017-01-25 09:23 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: pgsql connection timeone
2017-01-25 09:44 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: pgsql connection timeone
2017-01-25 13:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pgsql connection timeone
2017-01-28 10:03 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: pgsql connection timeone
2017-02-01 12:51 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: pgsql connection timeone
2017-02-01 17:11 UTC Vitalii Tymchyshyn <vit@tym.im>
` Re: pgsql connection timeone
2017-02-04 16:45 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: pgsql connection timeone
2017-02-04 18:38 UTC Vitalii Tymchyshyn <vit@tym.im>
` Re: pgsql connection timeone
2017-02-17 16:52 UTC Vucomir Ianculov <vukomir@os-ux.com>
[9+ messages in thread]
performance contradiction
2017-01-23 16:55 UTC Gabriel Dodan <gabriel.dodan@gmail.com>
` Re: performance contradiction
2017-02-15 08:25 UTC Feike Steenbergen <feikesteenbergen@gmail.com>
[2+ messages in thread]
Inaccurate GiST Index Cost Causes DB Contention
2017-02-09 18:48 UTC PC Drew <pc@soprisapps.com>
strange and slow joining of nested views
2017-02-03 21:23 UTC Titus von Boxberg <titus@elbe-informatik.de>
` Re: strange and slow joining of nested views
2017-02-04 05:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: strange and slow joining of nested views
2017-02-04 20:20 UTC Titus von Boxberg <titus@elbe-informatik.de>
[3+ messages in thread]
PSA: upgrade your extensions
2017-02-01 12:38 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: PSA: upgrade your extensions
2017-02-01 15:18 UTC Daniel Blanch Bataller <daniel.blanch.bataller@gmail.com>
` Re: PSA: upgrade your extensions
2017-02-01 19:48 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: PSA: upgrade your extensions
2017-02-02 12:24 UTC Merlin Moncure <mmoncure@gmail.com>
[4+ messages in thread]
Backup taking long time !!!
2017-01-20 11:24 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: Backup taking long time !!!
2017-01-20 11:34 UTC Madusudanan.B.N <b.n.madusudanan@gmail.com>
` Re: Backup taking long time !!!
2017-01-20 11:43 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: Backup taking long time !!!
2017-01-20 11:48 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Backup taking long time !!!
2017-01-20 11:52 UTC Madusudanan.B.N <b.n.madusudanan@gmail.com>
` Re: Backup taking long time !!!
2017-01-20 11:53 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: Backup taking long time !!!
2017-01-20 11:55 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Backup taking long time !!!
2017-01-20 12:22 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-20 12:57 UTC Vladimir Borodin <root@simply.name>
` Re: Backup taking long time !!!
2017-01-20 13:40 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-20 14:45 UTC Vladimir Borodin <root@simply.name>
` Re: Backup taking long time !!!
2017-01-20 15:06 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-20 16:44 UTC Vladimir Borodin <root@simply.name>
` Re: Backup taking long time !!!
2017-01-20 16:59 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-22 13:20 UTC julyanto SUTANDANG <julyanto@equnix.co.id>
` Re: Backup taking long time !!!
2017-01-22 13:36 UTC julyanto SUTANDANG <julyanto@equnix.co.id>
` Re: Backup taking long time !!!
2017-01-22 14:55 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-22 14:57 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-22 16:04 UTC julyanto SUTANDANG <julyanto@equnix.co.id>
` Re: Backup taking long time !!!
2017-01-22 16:37 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-22 17:03 UTC julyanto SUTANDANG <julyanto@equnix.co.id>
` Re: Backup taking long time !!!
2017-01-22 17:32 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-22 17:56 UTC julyanto SUTANDANG <julyanto@equnix.co.id>
` Re: Backup taking long time !!!
2017-01-23 06:44 UTC Vladimir Borodin <root@simply.name>
` Re: Backup taking long time !!!
2017-01-23 06:48 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-23 08:31 UTC Torsten Zuehlsdorff <mailinglists@toco-domains.de>
` Re: Backup taking long time !!!
2017-01-23 15:16 UTC Jim Nasby <Jim.Nasby@BlueTreble.com>
` Re: Backup taking long time !!!
2017-01-23 15:27 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-23 15:28 UTC Jim Nasby <Jim.Nasby@BlueTreble.com>
` Re: Backup taking long time !!!
2017-01-23 15:31 UTC Jim Nasby <Jim.Nasby@BlueTreble.com>
` Re: Backup taking long time !!!
2017-01-23 17:12 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Backup taking long time !!!
2017-01-23 17:20 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-23 17:23 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-23 17:32 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Backup taking long time !!!
2017-01-23 17:43 UTC Simon Riggs <simon@2ndquadrant.com>
` Re: Backup taking long time !!!
2017-01-23 17:47 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-23 17:49 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-24 00:08 UTC julyanto SUTANDANG <julyanto@equnix.co.id>
` Re: Backup taking long time !!!
2017-01-24 15:55 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Backup taking long time !!!
2017-01-24 16:15 UTC Rick Otten <rottenwindfish@gmail.com>
` Re: Backup taking long time !!!
2017-01-24 16:39 UTC Stephen Frost <sfrost@snowman.net>
` Re: Backup taking long time !!!
2017-01-31 15:20 UTC David Steele <david@pgmasters.net>
[42+ messages in thread]
Chaotic query planning ?
2017-01-19 14:37 UTC Philippe Ivaldi <pivaldi@ovya.fr>
` Re: Chaotic query planning ?
2017-01-19 16:05 UTC Albe Laurenz <laurenz.albe@wien.gv.at>
` Re: Chaotic query planning ?
2017-01-30 08:24 UTC Philippe Ivaldi <pivaldi@ovya.fr>
[3+ messages in thread]
optimizing immutable vs. stable function calls?
2017-01-18 22:36 UTC Karl Czajkowski <karlcz@isi.edu>
` Re: optimizing immutable vs. stable function calls?
2017-01-18 22:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: optimizing immutable vs. stable function calls?
2017-01-18 23:06 UTC Karl Czajkowski <karlcz@isi.edu>
` Re: optimizing immutable vs. stable function calls?
2017-01-18 23:06 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: optimizing immutable vs. stable function calls?
2017-01-18 23:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: optimizing immutable vs. stable function calls?
2017-01-18 23:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: optimizing immutable vs. stable function calls?
2017-01-19 00:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: optimizing immutable vs. stable function calls?
2017-01-19 02:45 UTC Karl Czajkowski <karlcz@isi.edu>
` Re: optimizing immutable vs. stable function calls?
2017-01-23 15:10 UTC Jim Nasby <Jim.Nasby@BlueTreble.com>
` Re: optimizing immutable vs. stable function calls?
2017-01-24 00:08 UTC Merlin Moncure <mmoncure@gmail.com>
[10+ messages in thread]
Optimization inner join
2017-01-19 10:08 UTC Clailson <clailson.dba@gmail.com>
` Re: Optimization inner join
2017-01-19 12:34 UTC Phillip Couto <phillip@couto.in>
` Re: Optimization inner join
2017-01-19 13:04 UTC Clailson <clailson.dba@gmail.com>
` Re: Optimization inner join
2017-01-19 13:18 UTC Phillip Couto <phillip@couto.in>
` Re: Optimization inner join
2017-01-19 13:23 UTC Gustavo Rezende Montesino <gustavo.montesino@trtsp.jus.br>
` Re: Optimization inner join
2017-01-19 13:30 UTC Vitalii Tymchyshyn <vit@tym.im>
` Re: Optimization inner join
2017-01-19 13:46 UTC Phillip Couto <phillip@couto.in>
` Re: Optimization inner join
2017-01-19 14:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Optimization inner join
2017-01-19 14:15 UTC Phillip Couto <phillip@couto.in>
` Re: Optimization inner join
2017-01-19 14:45 UTC Gustavo Rezende Montesino <gustavo.montesino@trtsp.jus.br>
[10+ messages in thread]
out of range error while restore using pgdump
2017-01-16 09:20 UTC Samir Magar <samirmagar8@gmail.com>
` Re: out of range error while restore using pgdump
2017-01-16 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Sort-of replication for reporting purposes
2017-01-06 19:24 UTC Ivan Voras <ivoras@gmail.com>
` Re: Sort-of replication for reporting purposes
2017-01-06 19:30 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: Sort-of replication for reporting purposes
2017-01-06 19:33 UTC Ivan Voras <ivoras@gmail.com>
` Re: Sort-of replication for reporting purposes
2017-01-06 19:33 UTC Rick Otten <rottenwindfish@gmail.com>
` Re: Sort-of replication for reporting purposes
2017-01-06 19:43 UTC Stephen Frost <sfrost@snowman.net>
` Re: Sort-of replication for reporting purposes
2017-01-12 17:48 UTC ProPAAS DBA <dba@propaas.com>
` Re: Sort-of replication for reporting purposes
2017-01-13 11:00 UTC Stuart Bishop <stuart@stuartbishop.net>
` Re: Sort-of replication for reporting purposes
2017-01-13 11:17 UTC Ivan Voras <ivoras@gmail.com>
` Re: Sort-of replication for reporting purposes
2017-01-13 11:47 UTC Phillip Couto <phillip@couto.in>
` Re: Sort-of replication for reporting purposes
2017-01-13 11:48 UTC Stuart Bishop <stuart@stuartbishop.net>
[10+ messages in thread]
How can I find the source of postgresql per-connection memory leaks?
2017-01-12 17:08 UTC Eric Jensen <ericcj@gmail.com>
` Re: How can I find the source of postgresql per-connection memory leaks?
2017-01-12 17:18 UTC Joshua D. Drake <jd@commandprompt.com>
[2+ messages in thread]
Unable to connect to server
2017-01-03 10:00 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: Unable to connect to server
2017-01-04 09:12 UTC Andreas Kretschmer <akretschmer@spamfence.net>
` Re: Unable to connect to server
2017-01-04 11:03 UTC Vucomir Ianculov <vukomir@os-ux.com>
` Re: Unable to connect to server
2017-01-04 11:12 UTC Andreas Kretschmer <akretschmer@spamfence.net>
[4+ messages in thread]
Performance issue with castings args of the function
2017-01-02 14:34 UTC Андрей Хозов <avkhozov@gmail.com>
` Re: Performance issue with castings args of the function
2017-01-02 15:17 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Performance issue with castings args of the function
2017-01-02 16:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Performance issue with castings args of the function
2017-01-02 16:52 UTC Андрей Хозов <avkhozov@gmail.com>
[4+ messages in thread]
copy vs. C function
2011-12-11 01:27 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2011-12-11 02:32 UTC Craig Ringer <ringerc@ringerc.id.au>
` Re: copy vs. C function
2011-12-11 02:35 UTC Sam Gendler <sgendler@ideasculptor.com>
` Re: copy vs. C function
2011-12-11 03:08 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2011-12-12 16:38 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: copy vs. C function
2011-12-13 14:29 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2011-12-14 06:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: copy vs. C function
2011-12-14 07:02 UTC idc danny <idcdanny@yahoo.com>
` Re: copy vs. C function
2011-12-14 13:14 UTC Kevin Martyn <kevin.martyn@enterprisedb.com>
` Re: copy vs. C function
2011-12-14 14:06 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2011-12-14 14:32 UTC idc danny <idcdanny@yahoo.com>
` Re: copy vs. C function
2011-12-14 15:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: copy vs. C function
2011-12-14 15:40 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2011-12-14 15:51 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2011-12-15 03:18 UTC Jon Nelson <jnelson+pgsql@jamponi.net>
` Re: copy vs. C function
2016-12-30 11:35 UTC rajmhn <rajmhn.ram@gmail.com>
[16+ messages in thread]
why we do not create indexes on master
2016-12-27 15:22 UTC Valerii Valeev <valerii.valeev@mail.ru>
` Re: why we do not create indexes on master
2016-12-27 16:04 UTC Andreas Kretschmer <akretschmer@spamfence.net>
` Re: why we do not create indexes on master
2016-12-27 16:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: why we do not create indexes on master
2016-12-27 17:38 UTC Valerii Valeev <valerii.valeev@mail.ru>
` Re: why we do not create indexes on master
2016-12-27 17:43 UTC ProPAAS DBA <dba@propaas.com>
` Re: why we do not create indexes on master
2016-12-27 17:48 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: why we do not create indexes on master
2016-12-28 00:02 UTC Valerii Valeev <valerii.valeev@mail.ru>
[7+ messages in thread]
Fwd: [pgsql-performance] Daily digest v1.4804 (8 messages)
2016-12-27 23:57 UTC Valerii Valeev <valerii.valeev@mail.ru>
Invalid page header in block 25561983 of relation pg_tblspc
2016-12-27 09:24 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: Invalid page header in block 25561983 of relation pg_tblspc
2016-12-27 11:01 UTC Michael Paquier <michael.paquier@gmail.com>
[2+ messages in thread]
bad performance
2016-12-17 22:25 UTC Gabliver Faluker <gabliver@gmail.com>
` Re: bad performance
2016-12-17 23:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: bad performance
2016-12-25 13:33 UTC Jeremy Harris <jgh@wizmail.org>
[3+ messages in thread]
How to vacuum entire database excluding some tables in PostgreSQL9.1.
2016-12-21 17:49 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: How to vacuum entire database excluding some tables in PostgreSQL9.1.
2016-12-21 18:16 UTC ProPAAS DBA <dba@propaas.com>
[2+ messages in thread]
Size of Temporary tablespace is increasing very much in postgresql 9.1.
2016-12-15 10:28 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
` Re: Size of Temporary tablespace is increasing very much in postgresql 9.1.
2016-12-17 01:57 UTC Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
` Re: Size of Temporary tablespace is increasing very much in postgresql 9.1.
2016-12-19 09:19 UTC Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
[3+ 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