pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedCustom opclass for column statistics?
2019-07-06 09:02 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: Custom opclass for column statistics?
2019-07-06 13:38 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Custom opclass for column statistics?
2019-07-06 13:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Custom opclass for column statistics?
2019-07-06 15:35 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: Custom opclass for column statistics?
2019-07-06 15:57 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Custom opclass for column statistics?
2019-07-06 23:17 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: Custom opclass for column statistics?
2019-07-09 22:16 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
[7+ messages in thread]
UUID v1 optimizations...
2019-05-25 13:45 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-25 14:19 UTC Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: UUID v1 optimizations...
2019-05-25 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: UUID v1 optimizations...
2019-05-25 17:27 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-25 18:20 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-25 19:00 UTC Vitalii Tymchyshyn <vit@tym.im>
` Re: UUID v1 optimizations...
2019-05-25 21:02 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-25 21:02 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-25 21:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: UUID v1 optimizations...
2019-05-25 22:14 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: UUID v1 optimizations...
2019-05-25 22:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: UUID v1 optimizations...
2019-05-25 23:00 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-25 23:44 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: UUID v1 optimizations...
2019-05-25 23:49 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-26 01:09 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: UUID v1 optimizations...
2019-05-26 04:27 UTC Morris de Oryx <morrisdeoryx@gmail.com>
` Re: UUID v1 optimizations...
2019-05-26 09:01 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-26 09:38 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-05-26 10:24 UTC Morris de Oryx <morrisdeoryx@gmail.com>
` Re: UUID v1 optimizations...
2019-05-26 10:37 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: UUID v1 optimizations...
2019-05-26 10:38 UTC Morris de Oryx <morrisdeoryx@gmail.com>
` Re: UUID v1 optimizations...
2019-05-26 10:46 UTC Morris de Oryx <morrisdeoryx@gmail.com>
` Re: UUID v1 optimizations...
2019-06-11 20:27 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: UUID v1 optimizations...
2019-07-08 00:26 UTC Peter Geoghegan <pg@bowt.ie>
` Re: UUID v1 optimizations...
2019-07-09 22:08 UTC Ancoron Luciferis <ancoron.luciferis@googlemail.com>
[25+ messages in thread]
scans on table fail to be excluded by partition bounds
2019-06-24 17:31 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: scans on table fail to be excluded by partition bounds
2019-06-25 10:48 UTC Steven Winfield <Steven.Winfield@cantabcapital.com>
` Re: scans on table fail to be excluded by partition bounds
2019-06-26 18:03 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: scans on table fail to be excluded by partition bounds
2019-06-26 22:09 UTC David Rowley <david.rowley@2ndquadrant.com>
[4+ messages in thread]
Max_connections limit
2019-06-26 07:13 UTC Daulat Ram <Daulat.Ram@exponential.com>
` Re: Max_connections limit
2019-06-26 09:05 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Max_connections limit
2019-06-26 09:15 UTC Hervé Schweitzer (HER) <herve.schweitzer@dbi-services.com>
` Re: Max_connections limit
2019-06-26 12:38 UTC Rick Otten <rottenwindfish@gmail.com>
` RE: Max_connections limit
2019-06-26 14:29 UTC Igor Neyman <ineyman@perceptron.com>
[5+ messages in thread]
Incorrect index used in few cases..
2019-06-18 13:11 UTC AminPG Jaffer <aminjaffer.pg@gmail.com>
` Re: Incorrect index used in few cases..
2019-06-18 13:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Incorrect index used in few cases..
2019-06-18 18:55 UTC AminPG Jaffer <aminjaffer.pg@gmail.com>
` Re: Incorrect index used in few cases..
2019-06-18 21:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Incorrect index used in few cases..
2019-06-18 21:49 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Incorrect index used in few cases..
2019-06-18 22:13 UTC Andres Freund <andres@anarazel.de>
` Re: Incorrect index used in few cases..
2019-06-18 22:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Incorrect index used in few cases..
2019-06-23 15:07 UTC AminPG Jaffer <aminjaffer.pg@gmail.com>
` Re: Incorrect index used in few cases..
2019-06-26 14:24 UTC AminPG Jaffer <aminjaffer.pg@gmail.com>
[9+ messages in thread]
materialized view refresh of a foreign table
2019-06-23 14:21 UTC Rick Otten <rottenwindfish@gmail.com>
` Re: materialized view refresh of a foreign table
2019-06-25 11:03 UTC Rick Otten <rottenwindfish@gmail.com>
[2+ messages in thread]
monitoring tuple_count vs dead_tuple_count
2019-06-23 14:24 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
Using indexes in RLS policies (sub)queries
2019-06-21 12:22 UTC Grégory EL MAJJOUTI <gelmajjouti@gmail.com>
EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 15:12 UTC Chris Wilson <chris.wilson@cantabcapital.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 15:56 UTC Simon Riggs <simon@2ndquadrant.com>
` RE: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 16:00 UTC Chris Wilson <chris.wilson@cantabcapital.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 16:18 UTC Simon Riggs <simon@2ndquadrant.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 16:30 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 16:51 UTC Simon Riggs <simon@2ndquadrant.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 18:09 UTC Michael Lewis <mlewis@entrata.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 18:13 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-20 18:16 UTC Michael Lewis <mlewis@entrata.com>
` Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-21 09:17 UTC Simon Riggs <simon@2ndquadrant.com>
` RE: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-21 09:20 UTC Chris Wilson <chris.wilson@cantabcapital.com>
` RE: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
2019-06-21 09:43 UTC Chris Wilson <chris.wilson@cantabcapital.com>
[12+ messages in thread]
wal_log_hints benchmarks
2019-06-14 13:46 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: wal_log_hints benchmarks
2019-06-17 02:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: wal_log_hints benchmarks
2019-06-17 07:53 UTC Fabio Pardi <f.pardi@portavita.eu>
[3+ messages in thread]
upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 08:20 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 08:58 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 11:07 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` RE: upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 11:23 UTC Greg Clough <Greg.Clough@ihsmarkit.com>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 11:31 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 15:06 UTC Stephen Frost <sfrost@snowman.net>
` Re: upgrade to PG11 on secondary fails (no initdb was launched)
2019-05-23 15:08 UTC Stephen Frost <sfrost@snowman.net>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-06-14 03:30 UTC Bruce Momjian <bruce@momjian.us>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-06-14 13:12 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-06-14 14:39 UTC Bruce Momjian <bruce@momjian.us>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-06-14 14:44 UTC Bruce Momjian <bruce@momjian.us>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-06-14 16:15 UTC Stephen Frost <sfrost@snowman.net>
` Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
2019-06-14 16:16 UTC Stephen Frost <sfrost@snowman.net>
[13+ messages in thread]
Strange query behaviour between 9.4 and 12beta1
2019-06-04 14:34 UTC Vasilis Ventirozos <v.ventirozos@gmail.com>
` Re: Strange query behaviour between 9.4 and 12beta1
2019-06-04 23:01 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[2+ messages in thread]
Shortest offline window on database migration
2019-05-30 15:08 UTC Haroldo Kerry <hkerry@callix.com.br>
` Re: Shortest offline window on database migration
2019-05-30 15:31 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` RE: Shortest offline window on database migration
2019-05-30 15:54 UTC Steven Winfield <Steven.Winfield@cantabcapital.com>
` Re: Shortest offline window on database migration
2019-05-30 16:23 UTC Haroldo Kerry <hkerry@callix.com.br>
` Re: Shortest offline window on database migration
2019-05-30 21:52 UTC Haroldo Kerry <hkerry@callix.com.br>
` Re: Shortest offline window on database migration
2019-05-31 01:41 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Shortest offline window on database migration
2019-05-31 02:49 UTC Ian Lawrence Barwick <barwick@gmail.com>
` Re: Shortest offline window on database migration
2019-05-31 09:40 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: Shortest offline window on database migration
2019-06-01 13:17 UTC Haroldo Kerry <hkerry@callix.com.br>
` Re: Shortest offline window on database migration
2019-06-04 20:18 UTC Stephen Frost <sfrost@snowman.net>
[10+ messages in thread]
Sv: JIT in PostgreSQL 12 ?
2019-05-29 08:48 UTC Andreas Joseph Krogh <andreas@visena.com>
` Re: Sv: JIT in PostgreSQL 12 ?
2019-05-29 09:13 UTC Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: Sv: JIT in PostgreSQL 12 ?
2019-05-29 09:16 UTC Andreas Joseph Krogh <andreas@visena.com>
` Re: Sv: JIT in PostgreSQL 12 ?
2019-05-31 23:38 UTC Justin Pryzby <pryzby@telsasoft.com>
[4+ messages in thread]
improve wals replay on secondary
2019-05-27 08:49 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: improve wals replay on secondary
2019-05-27 09:12 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: improve wals replay on secondary
2019-05-27 09:29 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: improve wals replay on secondary
2019-05-27 10:17 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: improve wals replay on secondary
2019-05-27 11:04 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: improve wals replay on secondary
2019-05-28 10:54 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: improve wals replay on secondary
2019-05-29 07:20 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: improve wals replay on secondary
2019-05-29 08:20 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: improve wals replay on secondary
2019-05-29 08:39 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: improve wals replay on secondary
2019-05-29 10:54 UTC Nikolay Samokhvalov <samokhvalov@gmail.com>
` Re: improve wals replay on secondary
2019-05-29 11:10 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: improve wals replay on secondary
2019-05-31 11:54 UTC Fabio Pardi <f.pardi@portavita.eu>
[12+ messages in thread]
JIT in PostgreSQL 12 ?
2019-05-29 08:02 UTC Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: JIT in PostgreSQL 12 ?
2019-05-29 09:37 UTC Andreas Karlsson <andreas@proxel.se>
[2+ messages in thread]
Use Postgres as a column store by creating one table per column
2019-05-22 04:28 UTC Lev Kokotov <lev.kokotov@gmail.com>
` Re: Use Postgres as a column store by creating one table per column
2019-05-22 04:43 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Use Postgres as a column store by creating one table per column
2019-05-23 05:08 UTC George Neuner <gneuner2@comcast.net>
` Re: Use Postgres as a column store by creating one table per column
2019-05-24 18:06 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Use Postgres as a column store by creating one table per column
2019-05-24 19:38 UTC Stephen Frost <sfrost@snowman.net>
` Re: Use Postgres as a column store by creating one table per column
2019-05-25 03:55 UTC Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
[6+ messages in thread]
Re: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans
2019-05-09 04:14 UTC Deepak Somaiya <deepsom@yahoo.com>
` RE: Re: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans
2019-05-17 06:42 UTC Naik, Sameer <Sameer_Naik@bmc.com>
` Re: Re: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans
2019-05-20 21:37 UTC Deepak Somaiya <deepsom@yahoo.com>
` Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans
2019-05-20 22:16 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` RE: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans
2019-05-23 06:37 UTC Naik, Sameer <Sameer_Naik@bmc.com>
` Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans
2019-05-23 17:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
Performance of archive logging in a PITR restore
2009-03-16 16:11 UTC Mark Steben <msteben@autorevenue.com>
` Re: Performance of archive logging in a PITR restore
2009-03-16 16:21 UTC Joshua D. Drake <jd@commandprompt.com>
` Re: Performance of archive logging in a PITR restore
2009-03-18 11:33 UTC Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
` Analyze results in more expensive query plan
2019-05-16 20:03 UTC Jeremy Altavilla <jeremyaltavilla@gmail.com>
` Re: Analyze results in more expensive query plan
2019-05-17 13:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Analyze results in more expensive query plan
2019-05-20 20:19 UTC Jeremy Altavilla <jeremyaltavilla@gmail.com>
` Re: Analyze results in more expensive query plan
2019-05-21 02:04 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: Analyze results in more expensive query plan
2019-05-22 22:21 UTC Jeremy Altavilla <jeremyaltavilla@gmail.com>
[8+ messages in thread]
pg_restore takes more time on creation of rules
2019-05-22 15:26 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 15:41 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 15:44 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 16:00 UTC Ron <ronljohnsonjr@gmail.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 16:02 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 16:27 UTC Ron <ronljohnsonjr@gmail.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 16:44 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pg_restore takes more time on creation of rules
2019-05-22 17:00 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[8+ messages in thread]
Log size in bytes of query result
2019-05-10 14:10 UTC Franklin Haut <franklin.haut@gmail.com>
` Re: Log size in bytes of query result
2019-05-10 16:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Log size in bytes of query result
2019-05-10 16:42 UTC Sergei Kornilov <sk@zsrv.org>
` Re: Log size in bytes of query result
2019-05-22 12:50 UTC Franklin Haut <franklin.haut@gmail.com>
` Re: Log size in bytes of query result
2019-05-22 13:15 UTC Dmitry Dolgov <9erthalion6@gmail.com>
[5+ messages in thread]
Temporarily very slow planning time after a big delete
2019-05-21 00:43 UTC Walter Smith <walter@carezone.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 01:00 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 01:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 02:04 UTC Walter Smith <walter@carezone.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 02:12 UTC Walter Smith <walter@carezone.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 02:15 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:12 UTC Walter Smith <walter@carezone.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:15 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:16 UTC Walter Smith <walter@carezone.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:17 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:26 UTC Walter Smith <walter@carezone.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:32 UTC didier <did447@gmail.com>
` Re: Temporarily very slow planning time after a big delete
2019-05-21 18:36 UTC Peter Geoghegan <pg@bowt.ie>
[13+ messages in thread]
Trying to handle db corruption 9.6
2019-05-20 14:39 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 14:49 UTC Flo Rance <trourance@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 15:00 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 16:07 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 16:20 UTC Bimal <internetuser2008@yahoo.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 17:20 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 20:55 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Trying to handle db corruption 9.6
2019-05-20 21:04 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Trying to handle db corruption 9.6
2019-05-21 09:01 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-21 13:07 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Trying to handle db corruption 9.6
2019-05-21 13:12 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Trying to handle db corruption 9.6
2019-05-21 16:37 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[12+ messages in thread]
using sequential scan instead of index for join with a union
2019-05-17 09:15 UTC Kent Tong <kent.tong.mo@gmail.com>
` Re: using sequential scan instead of index for join with a union
2019-05-17 09:23 UTC Sergei Kornilov <sk@zsrv.org>
` Re: using sequential scan instead of index for join with a union
2019-05-17 09:36 UTC Kent Tong <kent.tong.mo@gmail.com>
[3+ messages in thread]
Long Running Commits
2009-03-04 16:18 UTC Brad Nicholson <bnichols@ca.afilias.info>
` The wrong (?) query plan for queries with remote (postgres_fdw) tables
2019-05-14 16:08 UTC Vitaly Baranovsky <barvetalforums@gmail.com>
[2+ 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