pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ERROR: found xmin from before relfrozenxid
  2019-01-23 15:25 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-23 19:42 UTC  Jerry Sievers <gsievers19@comcast.net>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-24 06:32 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-24 14:14 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-25 08:18 UTC  Adrien NAYRAT <adrien.nayrat@anayrat.info>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-25 17:20 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-26 10:48 UTC  Adrien NAYRAT <adrien.nayrat@anayrat.info>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-26 10:56 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-26 10:59 UTC  Adrien NAYRAT <adrien.nayrat@anayrat.info>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-30 07:51 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-30 09:13 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-01-30 10:35 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-02-04 16:42 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-03-12 07:58 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-03-13 12:24 UTC  Adrien NAYRAT <adrien.nayrat@anayrat.info>
` Re: ERROR: found xmin from before relfrozenxid
  2019-03-13 12:29 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-03-13 12:48 UTC  Alexandre Arruda <adaldeia@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-03-13 12:59 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: found xmin from before relfrozenxid
  2019-03-13 15:30 UTC  Adrien NAYRAT <adrien.nayrat@anayrat.info>
  [19+ messages in thread]

Planner not choosing GIN index
  2019-03-13 01:44 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: Planner not choosing GIN index
  2019-03-13 09:10 UTC  Flo Rance <trourance@gmail.com>
` Re: Planner not choosing GIN index
  2019-03-13 13:55 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: Planner not choosing GIN index
  2019-03-13 14:20 UTC  Flo Rance <trourance@gmail.com>
  [4+ messages in thread]

shared buffers
  2005-08-29 16:23 UTC  Carlos Henrique Reimer <carlosreimer@yahoo.com.br>
` Re: shared buffers
  2005-08-30 01:27 UTC  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
` Re: shared buffers
  2005-08-30 01:54 UTC  Carlos Henrique Reimer <carlosreimer@yahoo.com.br>
` Re: shared buffers
  2005-08-30 02:08 UTC  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
` Re: shared buffers
  2005-08-30 02:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: shared buffers
  2005-08-30 07:05 UTC  William Yu <wyu@talisys.com>
` Re: shared buffers
  2005-09-05 02:56 UTC  Martin Nickel <martin@portant.com>
` Re: shared buffers
  2005-09-11 12:35 UTC  John A Meinel <john@arbash-meinel.com>
` shared_buffers
  2010-02-22 15:04 UTC  George Sexton <georges@mhsoftware.com>
` Re: shared_buffers
  2010-02-22 15:23 UTC  Kevin Grittner <Kevin.Grittner@wicourts.gov>
` Shared_buffers
  2019-03-11 08:12 UTC  Daulat Ram <Daulat.Ram@exponential.com>
` Re: Shared_buffers
  2019-03-12 08:29 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Shared_buffers
  2019-03-12 19:23 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Shared_buffers
  2019-03-12 20:03 UTC  MichaelDBA <MichaelDBA@sqlexec.com>
` Re: Shared_buffers
  2019-03-12 20:11 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Shared_buffers
  2019-03-12 20:11 UTC  MichaelDBA <MichaelDBA@sqlexec.com>
  [16+ messages in thread]

Performance regression related to parallel execution
  2019-03-11 19:19 UTC  Jinho Jung <jinhojun@usc.edu>

Wired execution in my benchmark using postgresql 9.6
  2019-03-11 14:14 UTC  tayeb merabti <tayeb.merabti@gmail.com>

Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations
  2019-03-08 14:39 UTC  Alexandru Lazarev <alexandru.lazarev@gmail.com>
` Re: Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations
  2019-03-08 15:15 UTC  Alban Hertroys <haramrae@gmail.com>
` Re: Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations
  2019-03-08 16:40 UTC  Alexandru Lazarev <alexandru.lazarev@gmail.com>
` Re: Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations
  2019-03-09 20:08 UTC  Rene Romero Benavides <rene.romero.b@gmail.com>
  [4+ messages in thread]

IS NOT DISTINCT FROM statement
  2019-03-08 11:30 UTC  Artur Zając <azajac@ang.com.pl>
` Re: IS NOT DISTINCT FROM statement
  2019-03-08 11:45 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: IS NOT DISTINCT FROM statement
  2019-03-08 12:13 UTC  David Rowley <david.rowley@2ndquadrant.com>
` RE: IS NOT DISTINCT FROM statement
  2019-03-08 12:25 UTC  Artur Zając <azajac@ang.com.pl>
` Re: IS NOT DISTINCT FROM statement
  2019-03-08 13:12 UTC  David Rowley <david.rowley@2ndquadrant.com>
` Re: IS NOT DISTINCT FROM statement
  2019-03-08 14:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

rusage (Re: Good afternoon.)
  2019-03-06 22:48 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: rusage (Re: Good afternoon.)
  2019-03-06 22:59 UTC  Julien Rouhaud <rjuju123@gmail.com>
  [2+ messages in thread]

Performance regressions found using sqlfuzz
  2019-02-11 22:29 UTC  Jung, Jinho <jinho.jung@gatech.edu>
` Re: Performance regressions found using sqlfuzz
  2019-02-12 12:00 UTC  Christoph Berg <myon@debian.org>
` Re: Performance regressions found using sqlfuzz
  2019-02-12 18:03 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Performance regressions found using sqlfuzz
  2019-02-14 17:27 UTC  Jung, Jinho <jinho.jung@gatech.edu>
` Re: Performance regressions found using sqlfuzz
  2019-02-15 16:20 UTC  Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Performance regressions found using sqlfuzz
  2019-02-15 16:44 UTC  Andres Freund <andres@anarazel.de>
` Re: Performance regressions found using sqlfuzz
  2019-02-16 22:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Performance regressions found using sqlfuzz
  2019-02-18 21:08 UTC  Jung, Jinho <jinho.jung@gatech.edu>
` Re: Performance regressions found using sqlfuzz
  2019-02-28 16:43 UTC  Jung, Jinho <jinho.jung@gatech.edu>
` Performance regressions found using sqlfuzz
  2019-03-06 21:41 UTC  Jinho Jung <jinhojun@usc.edu>
  [10+ messages in thread]

JIT performance question
  2019-03-06 17:16 UTC  Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: JIT performance question
  2019-03-06 17:42 UTC  Andres Freund <andres@anarazel.de>
` Re: JIT performance question
  2019-03-06 18:21 UTC  Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: JIT performance question
  2019-03-06 18:32 UTC  Andres Freund <andres@anarazel.de>
  [4+ messages in thread]

autovacuum just stop vacuuming specific table for 7 hours
  2019-03-06 16:47 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum just stop vacuuming specific table for 7 hours
  2019-03-06 17:05 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: autovacuum just stop vacuuming specific table for 7 hours
  2019-03-06 17:16 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
  [3+ messages in thread]

Server upgrade advice [xpost]
  2019-03-05 22:03 UTC  Rory Campbell-Lange <rory@campbell-lange.net>
` Re: Server upgrade advice [xpost]
  2019-03-06 05:04 UTC  Ian Harding <harding.ian@gmail.com>
  [2+ messages in thread]

pgstattuple_approx for toasted table
  2019-03-03 15:59 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pgstattuple_approx for toasted table
  2019-03-04 05:21 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

How to get the content of Bind variables
  2019-02-28 12:21 UTC  ROS Didier <didier.ros@edf.fr>
` Re: How to get the content of Bind variables
  2019-02-28 12:36 UTC  MichaelDBA <MichaelDBA@sqlexec.com>
` RE: How to get the content of Bind variables
  2019-02-28 12:47 UTC  ROS Didier <didier.ros@edf.fr>
` Re: How to get the content of Bind variables
  2019-02-28 16:01 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: How to get the content of Bind variables
  2019-02-28 16:12 UTC  ROS Didier <didier.ros@edf.fr>
` Re: How to get the content of Bind variables
  2019-02-28 16:19 UTC  Justin Pryzby <pryzby@telsasoft.com>
` RE: How to get the content of Bind variables
  2019-03-01 07:54 UTC  ROS Didier <didier.ros@edf.fr>
` Re: How to get the content of Bind variables
  2019-03-01 08:31 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: How to get the content of Bind variables
  2019-03-01 16:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` RE: How to get the content of Bind variables
  2019-03-01 18:47 UTC  ROS Didier <didier.ros@edf.fr>
` RE: How to get the content of Bind variables
  2019-03-01 20:41 UTC  legrand legrand <legrand_legrand@hotmail.com>
` RE: How to get the content of Bind variables
  2019-03-02 13:14 UTC  ROS Didier <didier.ros@edf.fr>
` RE: How to get the content of Bind variables
  2019-03-02 14:10 UTC  legrand legrand <legrand_legrand@hotmail.com>
` Re: How to get the content of Bind variables
  2019-03-02 15:56 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: How to get the content of Bind variables
  2019-03-02 16:33 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: How to get the content of Bind variables
  2019-03-02 16:33 UTC  Sergei Kornilov <sk@zsrv.org>
` RE: How to get the content of Bind variables
  2019-03-02 19:14 UTC  ROS Didier <didier.ros@edf.fr>
` RE: How to get the content of Bind variables
  2019-03-02 19:19 UTC  ROS Didier <didier.ros@edf.fr>
  [18+ messages in thread]

What is pg_stat_user_tables Showing NULL for last_autoanalyze & last_autovacuum
  2019-02-27 14:47 UTC  Fd Habash <fmhabash@gmail.com>
` Re: What is pg_stat_user_tables Showing NULL for last_autoanalyze & last_autovacuum
  2019-02-27 16:15 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: What is pg_stat_user_tables Showing NULL for last_autoanalyze & last_autovacuum
  2019-02-28 08:44 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: What is pg_stat_user_tables Showing NULL for last_autoanalyze &last_autovacuum
  2019-02-28 13:34 UTC  Fd Habash <fmhabash@gmail.com>
  [4+ messages in thread]

Query slow for new participants
  2019-02-25 10:41 UTC  Kim <support@mekong.be>
` Re: Query slow for new participants
  2019-02-25 16:16 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Query slow for new participants
  2019-02-25 19:23 UTC  support@mekong.be <support@mekong.be>
` Re: Query slow for new participants
  2019-02-25 23:22 UTC  support@mekong.be <support@mekong.be>
` Re: Query slow for new participants
  2019-02-25 23:59 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Query slow for new participants
  2019-02-26 00:30 UTC  MichaelDBA <MichaelDBA@sqlexec.com>
` Re: Query slow for new participants
  2019-02-26 19:08 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Query slow for new participants
  2019-02-26 21:39 UTC  support@mekong.be <support@mekong.be>
` Re: Query slow for new participants
  2019-02-27 07:58 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [9+ messages in thread]

Aggregate and many LEFT JOIN
  2019-02-22 15:14 UTC  kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-22 15:54 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-22 16:14 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-22 16:33 UTC  kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-22 17:18 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-22 18:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Aggregate and many LEFT JOIN
  2019-02-25 08:54 UTC  kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-25 09:44 UTC  kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-25 18:29 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-26 12:54 UTC  kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-26 13:51 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Aggregate and many LEFT JOIN
  2019-02-26 13:52 UTC  Jeff Janes <jeff.janes@gmail.com>
  [12+ messages in thread]

Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-23 21:05 UTC  Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-23 21:13 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 02:55 UTC  Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 06:41 UTC  David Rowley <david.rowley@2ndquadrant.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 07:03 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 07:25 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 17:45 UTC  Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 20:20 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 20:41 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 21:34 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 22:43 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 22:52 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 23:33 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-24 23:39 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 03:06 UTC  Gunther Schadow <gunther@pragmaticdata.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 03:06 UTC  Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 03:54 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 16:30 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 20:30 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 21:03 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
  2019-02-25 21:07 UTC  MichaelDBA <MichaelDBA@sqlexec.com>
  [21+ messages in thread]

Idle backends outside a transaction holding onto large amounts of memory / swap space?
  2019-02-25 10:36 UTC  Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: Idle backends outside a transaction holding onto large amounts of memory / swap space?
  2019-02-25 10:52 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [2+ messages in thread]

Slow query with aggregate and many LEFT JOINS
  2019-02-22 15:36 UTC  kimaidou <kimaidou@gmail.com>
` RE: Slow query with aggregate and many LEFT JOINS
  2019-02-22 19:47 UTC  Igor Neyman <ineyman@perceptron.com>
` RE: Slow query with aggregate and many LEFT JOINS
  2019-02-22 19:53 UTC  Igor Neyman <ineyman@perceptron.com>
  [3+ messages in thread]

neither CPU nor IO bound, but throttled performance
  2019-02-20 23:32 UTC  Gunther <raj@gusw.net>
` Re: neither CPU nor IO bound, but throttled performance
  2019-02-21 01:32 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: neither CPU nor IO bound, but throttled performance
  2019-02-21 09:08 UTC  Magnus Hagander <magnus@hagander.net>
` Re: neither CPU nor IO bound, but throttled performance
  2019-02-21 15:59 UTC  Gunther Schadow <gunther@pragmaticdata.com>
  [4+ messages in thread]

How can sort performance be so different
  2019-01-29 18:29 UTC  Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
  2019-01-29 18:33 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: How can sort performance be so different
  2019-01-29 18:36 UTC  Saurabh Nanda <saurabhnanda@gmail.com>
` Re: How can sort performance be so different
  2019-01-29 18:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: How can sort performance be so different
  2019-01-30 11:57 UTC  Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
  2019-01-30 23:54 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: How can sort performance be so different
  2019-01-31 13:29 UTC  Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
  2019-02-05 20:30 UTC  Merlin Moncure <mmoncure@gmail.com>
` Re: How can sort performance be so different
  2019-02-06 08:38 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: How can sort performance be so different
  2019-02-18 15:49 UTC  Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
  2019-02-20 21:35 UTC  Merlin Moncure <mmoncure@gmail.com>
` Re: How can sort performance be so different
  2019-02-20 21:42 UTC  Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
  2019-02-20 22:25 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: How can sort performance be so different
  2019-02-21 00:54 UTC  Peter Geoghegan <pg@bowt.ie>
  [14+ messages in thread]

Why isn't an index scan being used?
  2019-02-20 00:10 UTC  Abi Noda <a@abinoda.com>
` Re: Why isn't an index scan being used?
  2019-02-20 00:51 UTC  David Rowley <david.rowley@2ndquadrant.com>
` Re: Why isn't an index scan being used?
  2019-02-20 00:59 UTC  Abi Noda <a@abinoda.com>
` Re: Why isn't an index scan being used?
  2019-02-20 03:00 UTC  Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Why isn't an index scan being used?
  2019-02-20 04:29 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Why isn't an index scan being used?
  2019-02-20 04:37 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Why isn't an index scan being used?
  2019-02-20 04:58 UTC  Abi Noda <a@abinoda.com>
` Re: Why isn't an index scan being used?
  2019-02-20 08:05 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Why isn't an index scan being used?
  2019-02-20 14:58 UTC  Jeff Janes <jeff.janes@gmail.com>
  [9+ messages in thread]

index on jsonb col with 2D array inside the json
  2019-02-19 15:59 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: index on jsonb col with 2D array inside the json
  2019-02-19 16:28 UTC  Michael Lewis <mlewis@entrata.com>
` Re: index on jsonb col with 2D array inside the json
  2019-02-19 16:33 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: index on jsonb col with 2D array inside the json
  2019-02-19 16:41 UTC  Michael Lewis <mlewis@entrata.com>
` Re: index on jsonb col with 2D array inside the json
  2019-02-19 18:30 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
  [5+ messages in thread]

dsa_allocate() faliure
  2018-01-29 16:19 UTC  Rick Otten <rottenwindfish@gmail.com>
` Re: dsa_allocate() faliure
  2018-01-29 16:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: dsa_allocate() faliure
  2018-01-29 20:52 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2018-01-29 21:35 UTC  Rick Otten <rottenwindfish@gmail.com>
` Re: dsa_allocate() faliure
  2018-05-23 04:10 UTC  Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
  2018-05-23 04:44 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2018-05-23 14:06 UTC  Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
  2018-08-15 20:32 UTC  Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
  2018-08-15 22:42 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2018-08-25 14:46 UTC  Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
  2018-08-29 04:44 UTC  Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
  2018-10-05 02:16 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2018-11-13 13:08 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-21 14:26 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-22 16:09 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2018-11-23 14:31 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-23 16:10 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2018-11-26 15:26 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-26 15:38 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-26 15:52 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2018-11-26 16:00 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-26 18:45 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: dsa_allocate() faliure
  2018-11-27 03:00 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2018-11-27 08:02 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2018-11-30 19:20 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2018-11-30 20:46 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2018-12-02 22:45 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` RE: dsa_allocate() faliure
  2019-01-24 14:44 UTC  Arne Roland <A.Roland@index.de>
` RE: dsa_allocate() faliure
  2019-01-28 13:50 UTC  Arne Roland <A.Roland@index.de>
` Re: dsa_allocate() faliure
  2019-01-28 18:56 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-01-29 11:32 UTC  Fabio Isabettini <fisabettini@voipfuture.com>
` Re: dsa_allocate() faliure
  2019-01-30 03:13 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-01-30 09:53 UTC  Fabio Isabettini <fisabettini@voipfuture.com>
` RE: dsa_allocate() faliure
  2019-01-31 18:19 UTC  Arne Roland <A.Roland@index.de>
` Re: dsa_allocate() faliure
  2019-02-01 18:08 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-04 07:52 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2019-02-04 08:22 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` RE: dsa_allocate() faliure
  2019-02-04 20:31 UTC  Arne Roland <A.Roland@index.de>
` Re: dsa_allocate() faliure
  2019-02-04 21:47 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-06 23:21 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-07 10:10 UTC  Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
  2019-02-07 17:49 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-08 02:29 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-09 10:21 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: dsa_allocate() faliure
  2019-02-09 20:24 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-09 21:06 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-10 06:26 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: dsa_allocate() faliure
  2019-02-10 06:40 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: dsa_allocate() faliure
  2019-02-10 16:00 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-10 16:11 UTC  Sergei Kornilov <sk@zsrv.org>
` Re: dsa_allocate() faliure
  2019-02-10 16:50 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-10 22:45 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-10 23:33 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: dsa_allocate() faliure
  2019-02-11 00:02 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-11 00:11 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-11 00:24 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-11 01:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: dsa_allocate() faliure
  2019-02-13 00:52 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
  2019-02-17 22:21 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
  2019-02-18 09:11 UTC  Jakub Glapa <jakub.glapa@gmail.com>
  [60+ 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