pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedqueries with DISTINCT / GROUP BY giving different plans
2013-08-14 15:33 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-14 18:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-16 19:20 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-16 19:36 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-20 15:13 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-20 16:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-20 17:56 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-20 21:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-20 22:21 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: queries with DISTINCT / GROUP BY giving different plans
2013-08-20 23:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
Can query planner prefer a JOIN over a high-cost Function?
2013-08-20 18:06 UTC David McNett <pglists@macnugget.org>
` Re: Can query planner prefer a JOIN over a high-cost Function?
2013-08-20 19:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
DBT5 execution failed due to undefined symbol: PQescapeLiteral
2013-08-16 04:13 UTC amul sul <sul_amul@yahoo.co.in>
` Re: DBT5 execution failed due to undefined symbol: PQescapeLiteral
2013-08-16 07:26 UTC Albe Laurenz <laurenz.albe@wien.gv.at>
` Re: DBT5 execution failed due to undefined symbol: PQescapeLiteral
2013-08-20 07:13 UTC amulsul <sul_amul@yahoo.co.in>
[3+ messages in thread]
Create one query out of two
2013-08-17 20:19 UTC Robert DiFalco <robert.difalco@gmail.com>
` Re: Create one query out of two
2013-08-18 00:31 UTC Calvin Dodge <caldodge@gmail.com>
` Re: Create one query out of two
2013-08-18 20:23 UTC Kevin Grittner <kgrittn@ymail.com>
[3+ messages in thread]
Need some basic information
2013-08-14 05:38 UTC M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
` Re: Need some basic information
2013-08-16 00:57 UTC Josh Berkus <josh@agliodbs.com>
[2+ messages in thread]
Index on a range array
2013-08-13 20:47 UTC Daniel Cristian Cruz <danielcristian@gmail.com>
` Re: Index on a range array
2013-08-14 12:21 UTC Daniel Cristian Cruz <danielcristian@gmail.com>
` Re: Index on a range array
2013-08-15 07:30 UTC Heikki Linnakangas <hlinnakangas@vmware.com>
[3+ messages in thread]
Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 00:41 UTC Craig Ringer <craig@2ndquadrant.com>
` Re: Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 02:46 UTC Craig Ringer <craig@2ndquadrant.com>
` Re: Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 03:52 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 03:57 UTC Craig Ringer <craig@2ndquadrant.com>
` Re: Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 04:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 04:44 UTC Craig Ringer <craig@2ndquadrant.com>
` Re: Interesting case of IMMUTABLE significantly hurting performance
2013-08-14 19:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
subselect requires offset 0 for good performance.
2013-08-01 19:40 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-01 21:15 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-01 23:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: subselect requires offset 0 for good performance.
2013-08-02 01:22 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-02 07:37 UTC Vik Fearing <vik.fearing@dalibo.com>
` Re: subselect requires offset 0 for good performance.
2013-08-02 17:08 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-02 19:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: subselect requires offset 0 for good performance.
2013-08-02 19:58 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-02 20:26 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-02 20:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: subselect requires offset 0 for good performance.
2013-08-02 21:27 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-06 22:12 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-08 22:09 UTC Vik Fearing <vik.fearing@dalibo.com>
` Re: subselect requires offset 0 for good performance.
2013-08-13 21:01 UTC Scott Marlowe <scott.marlowe@gmail.com>
` Re: subselect requires offset 0 for good performance.
2013-08-13 22:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: subselect requires offset 0 for good performance.
2013-08-13 23:42 UTC Scott Marlowe <scott.marlowe@gmail.com>
[16+ messages in thread]
Efficient Correlated Update
2013-08-08 18:06 UTC Robert DiFalco <robert.difalco@gmail.com>
` Re: Efficient Correlated Update
2013-08-08 22:21 UTC Robert DiFalco <robert.difalco@gmail.com>
` Re: Efficient Correlated Update
2013-08-09 15:44 UTC Kevin Grittner <kgrittn@ymail.com>
` Re: Efficient Correlated Update
2013-08-09 15:49 UTC Klaus Ita <klaus@worstofall.com>
` Re: Efficient Correlated Update
2013-08-09 15:52 UTC Robert DiFalco <robert.difalco@gmail.com>
` Re: Efficient Correlated Update
2013-08-09 15:54 UTC Igor Neyman <ineyman@perceptron.com>
[6+ messages in thread]
Efficiently query for the most recent record for a given user
2013-08-07 18:12 UTC Robert DiFalco <robert.difalco@gmail.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 18:19 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 18:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 18:35 UTC Igor Neyman <ineyman@perceptron.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 18:39 UTC Robert DiFalco <robert.difalco@gmail.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 18:39 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 19:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 19:05 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-07 19:13 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: Efficiently query for the most recent record for a given user
2013-08-08 20:08 UTC Claudio Freire <klaussfreire@gmail.com>
[10+ messages in thread]
Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-02 13:43 UTC slapo@centrum.sk
` Re: Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-05 08:14 UTC slapo@centrum.sk
` Re: Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-06 19:01 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 12:42 UTC slapo@centrum.sk
` Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 13:46 UTC Igor Neyman <ineyman@perceptron.com>
` RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 14:42 UTC slapo@centrum.sk
` Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 14:48 UTC Igor Neyman <ineyman@perceptron.com>
` Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 14:48 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 14:49 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 15:33 UTC slapo@centrum.sk
` Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 15:50 UTC Igor Neyman <ineyman@perceptron.com>
` Re: RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-07 15:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [PERFORM] RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
2013-08-08 06:59 UTC slapo@centrum.sk
[13+ messages in thread]
Better performance possible for a pathological query?
2013-08-07 15:38 UTC Alexis Lê-Quôc <alq@datadoghq.com>
` Re: Better performance possible for a pathological query?
2013-08-07 16:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Better performance possible for a pathological query?
2013-08-07 16:28 UTC Alexis Lê-Quôc <alq@datadoghq.com>
[3+ messages in thread]
ORDER BY, LIMIT and indexes
2013-08-05 23:04 UTC Ivan Voras <ivoras@freebsd.org>
` Re: ORDER BY, LIMIT and indexes
2013-08-05 23:25 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 00:20 UTC Michael Paquier <michael.paquier@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 01:22 UTC Josh Berkus <josh@agliodbs.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 01:42 UTC Sergey Konoplev <gray.ru@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 01:54 UTC David Johnston <polobo@yahoo.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 10:04 UTC Ivan Voras <ivoras@freebsd.org>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 10:46 UTC Ivan Voras <ivoras@freebsd.org>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 15:47 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 16:09 UTC Nikolas Everett <nik9000@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 16:57 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 22:56 UTC Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 23:03 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 23:09 UTC Claudio Freire <klaussfreire@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-06 23:50 UTC Sergey Konoplev <gray.ru@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-07 00:00 UTC Sergey Konoplev <gray.ru@gmail.com>
` Re: ORDER BY, LIMIT and indexes
2013-08-07 04:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[17+ messages in thread]
PG performance issues related to storage I/O waits
2013-07-31 11:58 UTC Tasos Petalas <tasos.petalas@upstreamsystems.com>
` Re: PG performance issues related to storage I/O waits
2013-07-31 12:40 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: PG performance issues related to storage I/O waits
2013-08-01 02:02 UTC KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>
` Re: PG performance issues related to storage I/O waits
2013-08-03 20:38 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: PG performance issues related to storage I/O waits
2013-08-05 20:28 UTC Tomas Vondra <tv@fuzzy.cz>
` Re: PG performance issues related to storage I/O waits
2013-08-06 04:46 UTC Tasos Petalas <tasos.petalas@upstreamsystems.com>
[6+ messages in thread]
Looks like merge join planning time is too big, 55 seconds
2013-08-01 09:55 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 10:04 UTC Thomas Reiss <thomas.reiss@dalibo.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 11:27 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 11:45 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 14:30 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 15:17 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 17:58 UTC David Kerr <dmk@mr-paradox.net>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 18:23 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 19:13 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 19:51 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-01 21:50 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 00:16 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 03:19 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 15:29 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 15:35 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 16:20 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 16:23 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 17:11 UTC Sergey Burladyan <eshkinkot@gmail.com>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 19:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Looks like merge join planning time is too big, 55 seconds
2013-08-02 21:17 UTC Sergey Burladyan <eshkinkot@gmail.com>
[21+ messages in thread]
to many locks held
2013-07-30 10:52 UTC Jeison Bedoya <jeisonb@audifarma.com.co>
` Re: to many locks held
2013-07-30 14:48 UTC bricklen <bricklen@gmail.com>
` Re: to many locks held
2013-07-31 05:18 UTC Michael Paquier <michael.paquier@gmail.com>
` Re: to many locks held
2013-08-02 21:03 UTC Kevin Grittner <kgrittn@ymail.com>
[4+ messages in thread]
Fw: [osdldbt-general] Running DBT5 on remote database server
2013-07-23 02:13 UTC amul sul <sul_amul@yahoo.co.in>
` Re: Fw: [osdldbt-general] Running DBT5 on remote database server
2013-07-25 13:03 UTC Samrat Revagade <revagade.samrat@gmail.com>
` Re: Fw: [osdldbt-general] Running DBT5 on remote database server
2013-07-25 13:26 UTC sachin kotwal <kotsachin@gmail.com>
` Re: Fw: [osdldbt-general] Running DBT5 on remote database server
2013-07-31 16:02 UTC Greg Smith <greg@2ndQuadrant.com>
[4+ messages in thread]
FTS performance issue - planner problem identified (but only partially resolved)
2013-07-18 23:39 UTC Stefan Keller <sfkeller@gmail.com>
` Re: FTS performance issue - planner problem identified (but only partially resolved)
2013-07-19 13:38 UTC Stefan Keller <sfkeller@gmail.com>
` Re: FTS performance issue - planner problem identified (but only partially resolved)
2013-07-19 19:57 UTC Marc Mamin <M.Mamin@intershop.de>
` Re: FTS performance issue - planner problem identified (but only partially resolved)
2013-07-19 23:55 UTC Stefan Keller <sfkeller@gmail.com>
` Re: FTS performance issue - planner problem identified (but only partially resolved)
2013-07-20 08:46 UTC Marc Mamin <M.Mamin@intershop.de>
` Re: FTS performance issue - planner problem identified (but only partially resolved)
2013-07-29 20:28 UTC Kevin Grittner <kgrittn@ymail.com>
` Re: FTS performance issue - planner problem identified (but only partially resolved)
2013-07-29 23:29 UTC Stefan Keller <sfkeller@gmail.com>
[7+ messages in thread]
How is memory allocated/used by Postgresql Database connections
2013-07-25 13:23 UTC McKinzie, Alan (Alan) <alanmck@avaya.com>
` Re: How is memory allocated/used by Postgresql Database connections
2013-07-25 13:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: How is memory allocated/used by Postgresql Database connections
2013-07-25 17:32 UTC Jeff Janes <jeff.janes@gmail.com>
[3+ messages in thread]
Fwd: Relatively high planner overhead on partitions?
2013-07-19 13:52 UTC Skarsol <skarsol@gmail.com>
` Re: Fwd: Relatively high planner overhead on partitions?
2013-07-19 16:16 UTC Pavel Stehule <pavel.stehule@gmail.com>
[2+ messages in thread]
How to properly index hstore tags column to faster search for keys
2013-07-07 07:28 UTC Radu-Stefan Zugravu <raduzugravu90@gmail.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 07:44 UTC Richard Huxton <dev@archonet.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 08:31 UTC Radu-Stefan Zugravu <raduzugravu90@gmail.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 08:53 UTC Richard Huxton <dev@archonet.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 09:20 UTC Radu-Stefan Zugravu <raduzugravu90@gmail.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 10:27 UTC Richard Huxton <dev@archonet.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 11:01 UTC Radu-Stefan Zugravu <raduzugravu90@gmail.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 12:16 UTC idc danny <idcdanny@yahoo.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-08 15:34 UTC Yuri Levinsky <yuril@celltick.com>
` Re: How to properly index hstore tags column to faster search for keys
2013-07-19 10:03 UTC Stefan Keller <sfkeller@gmail.com>
[10+ messages in thread]
PostgreSQL settings for running on an SSD drive
2013-06-20 19:56 UTC CS DBA <cs_dba@consistentstate.com>
` Re: PostgreSQL settings for running on an SSD drive
2013-06-20 20:13 UTC Shaun Thomas <sthomas@optionshouse.com>
` Re: PostgreSQL settings for running on an SSD drive
2013-06-20 20:32 UTC Josh Berkus <josh@agliodbs.com>
` Re: PostgreSQL settings for running on an SSD drive
2013-06-20 21:23 UTC Shaun Thomas <sthomas@optionshouse.com>
` Re: PostgreSQL settings for running on an SSD drive
2013-06-20 21:32 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: PostgreSQL settings for running on an SSD drive
2013-07-18 02:04 UTC Greg Smith <greg@2ndQuadrant.com>
` Re: PostgreSQL settings for running on an SSD drive
2013-07-18 20:42 UTC Shaun Thomas <sthomas@optionshouse.com>
[7+ messages in thread]
bgwriter autotuning might be unnecessarily penalizing bursty workloads
2013-07-17 22:46 UTC Josh Berkus <josh@agliodbs.com>
` Re: bgwriter autotuning might be unnecessarily penalizing bursty workloads
2013-07-18 01:15 UTC Greg Smith <greg@2ndQuadrant.com>
` Re: Re: bgwriter autotuning might be unnecessarily penalizing bursty workloads
2013-07-18 17:40 UTC Josh Berkus <josh@agliodbs.com>
` Re: Re: bgwriter autotuning might be unnecessarily penalizing bursty workloads
2013-07-18 19:24 UTC Jeff Janes <jeff.janes@gmail.com>
[4+ messages in thread]
Seq Scan vs Index on Identical Tables in Two Different Databases
2013-07-17 19:50 UTC Ellen Rothman <erothman@datalinedata.com>
` Re: Seq Scan vs Index on Identical Tables in Two Different Databases
2013-07-17 20:11 UTC bricklen <bricklen@gmail.com>
` Re: Seq Scan vs Index on Identical Tables in Two Different Databases
2013-07-17 21:14 UTC David Johnston <polobo@yahoo.com>
` Re: Seq Scan vs Index on Identical Tables in Two Different Databases
2013-07-17 21:40 UTC David Kerr <dmk@mr-paradox.net>
` Re: Seq Scan vs Index on Identical Tables in Two Different Databases
2013-07-17 21:54 UTC Ellen Rothman <erothman@datalinedata.com>
[5+ messages in thread]
Distributed transactions and asynchronous commit
2013-07-17 07:18 UTC Xenofon Papadopoulos <xpapad@gmail.com>
` Re: Distributed transactions and asynchronous commit
2013-07-17 09:28 UTC Vasilis Ventirozos <v.ventirozos@gmail.com>
` Re: Distributed transactions and asynchronous commit
2013-07-17 10:09 UTC Giuseppe Broccolo <giuseppe.broccolo@2ndquadrant.it>
` Re: Distributed transactions and asynchronous commit
2013-07-17 10:52 UTC Xenofon Papadopoulos <xpapad@gmail.com>
` Re: Distributed transactions and asynchronous commit
2013-07-17 11:16 UTC Giuseppe Broccolo <giuseppe.broccolo@2ndquadrant.it>
` Re: Distributed transactions and asynchronous commit
2013-07-17 11:21 UTC Vasilis Ventirozos <v.ventirozos@gmail.com>
` Re: Distributed transactions and asynchronous commit
2013-07-17 11:26 UTC Vasilis Ventirozos <v.ventirozos@gmail.com>
` Re: Distributed transactions and asynchronous commit
2013-07-17 12:18 UTC Xenofon Papadopoulos <xpapad@gmail.com>
[8+ 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