pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
***Conflict with recovery error***
  2023-01-20 08:56 UTC  Abhishek Prakash <abhishek.prakash08@infosys.com>
` Re: ***Conflict with recovery error***
  2023-01-20 09:55 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: ***Conflict with recovery error***
  2023-01-20 09:59 UTC  Abhishek Prakash <abhishek.prakash08@infosys.com>
` Re: ***Conflict with recovery error***
  2023-01-20 10:08 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [4+ messages in thread]

Documentation discrepancy UNIQUE NULLS NOT DISTINCT
  2023-01-19 22:41 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Documentation discrepancy UNIQUE NULLS NOT DISTINCT
  2023-01-19 22:51 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

minor bug
  2023-01-16 18:59 UTC  Torsten Förtsch <tfoertsch123@gmail.com>
` Re: minor bug
  2023-01-17 09:42 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: minor bug
  2023-01-17 10:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: minor bug
  2023-01-17 15:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: minor bug
  2023-01-18 08:27 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: minor bug
  2023-01-18 20:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: minor bug
  2023-01-19 12:57 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: minor bug
  2023-01-19 17:18 UTC  Torsten Förtsch <tfoertsch123@gmail.com>
` Re: minor bug
  2023-01-19 17:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: minor bug
  2023-01-19 17:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [10+ messages in thread]

row estimate for partial index
  2023-01-13 15:01 UTC  Harmen <harmen@lijzij.de>
` Re: row estimate for partial index
  2023-01-14 16:23 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: row estimate for partial index
  2023-01-16 08:55 UTC  Harmen <harmen@lijzij.de>
` Re: row estimate for partial index
  2023-01-16 14:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: row estimate for partial index
  2023-01-19 09:04 UTC  Harmen <harmen@lijzij.de>
  [5+ messages in thread]

Database size different on Primary and Standby?
  2023-01-18 23:09 UTC  Hilbert, Karin <ioh1@psu.edu>
` Re: Database size different on Primary and Standby?
  2023-01-18 23:50 UTC  Erik Wienhold <ewie@ewie.name>
` Re: Database size different on Primary and Standby?
  2023-01-19 00:23 UTC  Ian Lawrence Barwick <barwick@gmail.com>
` Re: Database size different on Primary and Standby?
  2023-01-19 00:47 UTC  Erik Wienhold <ewie@ewie.name>
` Re: Database size different on Primary and Standby?
  2023-01-19 01:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Database size different on Primary and Standby?
  2023-01-19 02:13 UTC  Ron <ronljohnsonjr@gmail.com>
  [6+ messages in thread]

Tools for moving normalized data around
  2023-01-18 19:47 UTC  Peter <pmc@citylink.dinoex.sub.org>
` Re: Tools for moving normalized data around
  2023-01-18 20:02 UTC  Jeremy Smith <jeremy@musicsmith.net>
` Re: Tools for moving normalized data around
  2023-01-18 20:15 UTC  Gavan Schneider <list.pg.gavan@pendari.org>
` Re: Tools for moving normalized data around
  2023-01-18 20:19 UTC  Dominique Devienne <ddevienne@gmail.com>
` Re: Tools for moving normalized data around
  2023-01-18 20:45 UTC  Rob Sargent <robjsargent@gmail.com>
  [5+ messages in thread]

Interpreting postgres execution plan along with AND/OR precedence
  2023-01-18 17:03 UTC  Dirschel, Steve <steve.dirschel@thomsonreuters.com>
` Re: Interpreting postgres execution plan along with AND/OR precedence
  2023-01-18 17:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Interpreting postgres execution plan along with AND/OR precedence
  2023-01-18 18:14 UTC  Erik Wienhold <ewie@ewie.name>
` Re: Interpreting postgres execution plan along with AND/OR precedence
  2023-01-18 18:21 UTC  Erik Wienhold <ewie@ewie.name>
  [4+ messages in thread]

Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-15 15:47 UTC  HECTOR INGERTO <HECTOR_25E@hotmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-15 19:36 UTC  Magnus Hagander <magnus@hagander.net>
` RE: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-15 21:57 UTC  HECTOR INGERTO <hector_25e@hotmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-15 22:07 UTC  Magnus Hagander <magnus@hagander.net>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-15 22:26 UTC  Ron <ronljohnsonjr@gmail.com>
` RE: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-16 08:41 UTC  HECTOR INGERTO <hector_25e@hotmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-16 13:21 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-16 14:37 UTC  HECTOR INGERTO <hector_25e@hotmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-17 08:05 UTC  Alban Hertroys <haramrae@gmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-17 08:19 UTC  Magnus Hagander <magnus@hagander.net>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-17 08:26 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-17 15:22 UTC  HECTOR INGERTO <hector_25e@hotmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-17 21:38 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-18 10:02 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-18 16:38 UTC  HECTOR INGERTO <hector_25e@hotmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-18 16:54 UTC  Rob Sargent <robjsargent@gmail.com>
` Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
  2023-01-18 17:26 UTC  Ron <ronljohnsonjr@gmail.com>
  [17+ messages in thread]

Tablespace OID, database OID, relfilenode
  2023-01-17 14:48 UTC  Wiwwo Staff <wiwwo@wiwwo.com>
` Re: Tablespace OID, database OID, relfilenode
  2023-01-17 15:01 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Tablespace OID, database OID, relfilenode
  2023-01-17 15:35 UTC  Wiwwo Staff <wiwwo@wiwwo.com>
` Re: Tablespace OID, database OID, relfilenode
  2023-01-17 15:43 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Tablespace OID, database OID, relfilenode
  2023-01-17 15:44 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Tablespace OID, database OID, relfilenode
  2023-01-17 19:49 UTC  Wiwwo Staff <wiwwo@wiwwo.com>
` Re: Tablespace OID, database OID, relfilenode
  2023-01-18 05:27 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
  [7+ messages in thread]

Maintaining blank lines in psql output?
  2023-01-17 20:48 UTC  Ron <ronljohnsonjr@gmail.com>
` Re: Maintaining blank lines in psql output?
  2023-01-17 21:22 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Maintaining blank lines in psql output?
  2023-01-17 23:06 UTC  raf <raf@raf.org>
` Re: Maintaining blank lines in psql output?
  2023-01-17 23:10 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Maintaining blank lines in psql output?
  2023-01-17 23:21 UTC  raf <raf@raf.org>
` Re: Maintaining blank lines in psql output?
  2023-01-18 00:22 UTC  Ron <ronljohnsonjr@gmail.com>
  [6+ messages in thread]

pg_upgrade 13.6 to 15.1?
  2023-01-15 19:27 UTC  pf@pfortin.com
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 19:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 20:23 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 20:39 UTC  pf@pfortin.com
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 20:41 UTC  pf@pfortin.com
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 20:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 21:00 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 21:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 21:27 UTC  pf@pfortin.com
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 21:38 UTC  pf@pfortin.com
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 21:59 UTC  pf@pfortin.com
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 22:15 UTC  Alan Hodgson <ahodgson@lists.simkin.ca>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 22:16 UTC  Gavan Schneider <list.pg.gavan@pendari.org>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-15 22:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade 13.6 to 15.1?
  2023-01-17 21:41 UTC  Bruce Momjian <bruce@momjian.us>
  [15+ messages in thread]

Use case for enabling log_duration other than benchmarking
  2023-01-10 13:14 UTC  Alicja Kucharczyk <zaledwie10minut@gmail.com>
` Re: Use case for enabling log_duration other than benchmarking
  2023-01-10 13:57 UTC  Ron <ronljohnsonjr@gmail.com>
` Re: Use case for enabling log_duration other than benchmarking
  2023-01-10 15:57 UTC  Alicja Kucharczyk <zaledwie10minut@gmail.com>
` Re: Use case for enabling log_duration other than benchmarking
  2023-01-10 16:28 UTC  Ron <ronljohnsonjr@gmail.com>
` Re: Use case for enabling log_duration other than benchmarking
  2023-01-11 05:02 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: Use case for enabling log_duration other than benchmarking
  2023-01-17 21:26 UTC  Bruce Momjian <bruce@momjian.us>
  [6+ messages in thread]

https://wiki.postgresql.org/wiki/Working_with_Git link one link cannot open, another link is unrelated.
  2022-12-28 10:01 UTC  jian he <jian.universality@gmail.com>
` Re: https://wiki.postgresql.org/wiki/Working_with_Git link one link cannot open, another link is unrelated.
  2022-12-29 09:51 UTC  Melih Mutlu <m.melihmutlu@gmail.com>
` Re: https://wiki.postgresql.org/wiki/Working_with_Git link one link cannot open, another link is unrelated.
  2023-01-17 18:05 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
  [3+ messages in thread]

pg_stat_all_tables: n_live_tup column value not persisting
  2023-01-17 06:15 UTC  pran d <dpran433@gmail.com>

synchronized standby: committed local and waiting for remote ack
  2023-01-14 03:16 UTC  qihua wu <staywithpin@gmail.com>
` Re: synchronized standby: committed local and waiting for remote ack
  2023-01-14 05:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: synchronized standby: committed local and waiting for remote ack
  2023-01-17 03:06 UTC  qihua wu <staywithpin@gmail.com>
  [3+ messages in thread]

Why is a Read-only Table Gets Autovacuumed "to prevent wraparound"
  2023-01-16 12:48 UTC  Fred Habash <fmhabash@gmail.com>
` Re: Why is a Read-only Table Gets Autovacuumed "to prevent wraparound"
  2023-01-16 13:11 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Why is a Read-only Table Gets Autovacuumed "to prevent wraparound"
  2023-01-16 14:32 UTC  Erik Wienhold <ewie@ewie.name>
` Re: Why is a Read-only Table Gets Autovacuumed "to prevent wraparound"
  2023-01-16 21:18 UTC  Ron <ronljohnsonjr@gmail.com>
` Re: Why is a Read-only Table Gets Autovacuumed "to prevent wraparound"
  2023-01-16 21:46 UTC  Rob Sargent <robjsargent@gmail.com>
` Re: Why is a Read-only Table Gets Autovacuumed "to prevent wraparound"
  2023-01-16 23:13 UTC  Ron <ronljohnsonjr@gmail.com>
  [6+ messages in thread]

No function matches the given name and argument types.
  2023-01-16 16:04 UTC  arons <arons7@gmail.com>
` Re: No function matches the given name and argument types.
  2023-01-16 16:17 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: No function matches the given name and argument types.
  2023-01-16 16:21 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: No function matches the given name and argument types.
  2023-01-16 17:41 UTC  arons <arons7@gmail.com>
` Re: No function matches the given name and argument types.
  2023-01-16 17:49 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: No function matches the given name and argument types.
  2023-01-16 17:53 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: No function matches the given name and argument types.
  2023-01-16 17:57 UTC  Christophe Pettus <xof@thebuild.com>
  [7+ messages in thread]

glibc initdb options vs icu compatibility questions (PG15)
  2023-01-16 08:30 UTC  Robert Sjöblom <robert.sjoblom@fortnox.se>
` Re: glibc initdb options vs icu compatibility questions (PG15)
  2023-01-16 13:26 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: glibc initdb options vs icu compatibility questions (PG15)
  2023-01-16 15:47 UTC  Joe Conway <mail@joeconway.com>
  [3+ messages in thread]

AW: AW: [Extern] Re: postgres restore & needed history files
  2023-01-13 11:23 UTC  Zwettler Markus (OIZ) <Markus.Zwettler@zuerich.ch>
` Re: AW: AW: [Extern] Re: postgres restore & needed history files
  2023-01-16 13:30 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

does refreshing materialized view make the database bloat?
  2023-01-14 06:04 UTC  jian he <jian.universality@gmail.com>
` Re: does refreshing materialized view make the database bloat?
  2023-01-14 06:19 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: does refreshing materialized view make the database bloat?
  2023-01-14 08:51 UTC  Peter J. Holzer <hjp-pgsql@hjp.at>
` Re: does refreshing materialized view make the database bloat?
  2023-01-16 04:52 UTC  jian he <jian.universality@gmail.com>
` Re: does refreshing materialized view make the database bloat?
  2023-01-16 04:58 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: does refreshing materialized view make the database bloat?
  2023-01-16 05:29 UTC  jian he <jian.universality@gmail.com>
` Re: does refreshing materialized view make the database bloat?
  2023-01-16 05:43 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [7+ messages in thread]

Re: pg_upgrade 13.6 to 15.1?  [Solved: what can go wrong, will...]
  2023-01-15 22:56 UTC  pf@pfortin.com

SQL Question
  1999-03-10 05:45 UTC  Matthew <matt@ctlno.com>
` RE: [GENERAL] SQL Question
  1999-03-10 06:05 UTC  Michael Davis <michael.davis@prevuenet.com>
` sql question
  1999-11-17 19:53 UTC  Herbert Liechti <Herbert.Liechti@thinx.ch>
` Re: [GENERAL] sql question
  1999-11-18 12:32 UTC  Herbert Liechti <Herbert.Liechti@thinx.ch>
` Re: sql question
  1999-11-18 16:37 UTC  Ed Loehr <ELOEHR@austin.rr.com>
` Re: [GENERAL] Re: sql question
  1999-11-18 21:09 UTC  Herbert Liechti <Herbert.Liechti@thinx.ch>
` Re: [GENERAL] Re: sql question
  1999-11-19 00:17 UTC  Ed Loehr <ELOEHR@austin.rr.com>
` Re: [GENERAL] Re: sql question
  1999-11-19 07:06 UTC  Herbert Liechti <Herbert.Liechti@thinx.ch>
` sql question
  2000-01-14 22:16 UTC  rut <rutl@earthlink.net>
` SQL question
  2000-07-10 10:37 UTC  Travis Bauer <trbauer@indiana.edu>
` Re: SQL question
  2000-07-10 12:27 UTC  NRonayette <r97m10@socotec.fr>
` sql question
  2000-07-12 22:33 UTC  Travis Bauer <trbauer@indiana.edu>
` Re: sql question
  2000-07-12 23:25 UTC  Ross J. Reedstrom <reedstrm@rice.edu>
` Re: sql question
  2000-07-13 10:18 UTC  Travis Bauer <trbauer@indiana.edu>
` sql question
  2000-09-27 19:11 UTC  chris markiewicz <cmarkiew@commnav.com>
` Re: sql question
  2000-09-27 19:20 UTC  Adam Lang <aalang@rutgersinsurance.com>
` SQL question
  2000-11-23 15:23 UTC  Igor' Robul' <igor@raduga.dyndns.org>
` SQL Question
  2001-02-22 21:13 UTC  Matthew <matt@ctlno.com>
` Re: SQL Question
  2001-02-22 21:37 UTC  Mitch Vincent <mitch@venux.net>
` SQL Question
  2001-03-08 18:36 UTC  Matthew <matt@ctlno.com>
` Re: SQL Question
  2001-03-08 20:13 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` sql question
  2001-05-13 18:45 UTC  u95886230@spawnkill.ip-mobilphone.net
` Re: sql question
  2001-05-15 10:45 UTC  Justin Clift <justin@postgresql.org>
` Re: sql question
  2001-05-16 05:26 UTC  will trillich <will@serensoft.com>
` Re: sql question
  2001-05-16 20:03 UTC  Joel Burton <jburton@scw.org>
` Re: sql question
  2001-05-21 00:44 UTC  Blackin <rblackin@home.com>
` SQL question
  2001-11-02 01:17 UTC  Johnson, Shaunn <SJohnson6@bcbsm.com>
` SQL question..
  2002-04-17 16:50 UTC  Alexis Maldonado <amaldona@ctcd.cc.tx.us>
` Re: SQL question..
  2002-04-18 08:05 UTC  Petr Bravenec <pbravenec@solartec.cz>
` SQL question
  2003-06-09 13:30 UTC  Guillaume Houssay <ghoussay@noos.fr>
` Re: SQL question
  2003-06-10 05:32 UTC  Martijn van Oosterhout <kleptog@svana.org>
` Re: SQL question
  2003-06-10 07:04 UTC  Richard Huxton <dev@archonet.com>
` SQL question
  2003-06-19 16:36 UTC  Együd Csaba <csegyud@freemail.hu>
` Re: SQL question
  2003-06-19 18:37 UTC  Richard Huxton <dev@archonet.com>
` SQL  (?) question
  2004-07-20 20:31 UTC  Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
` Re: SQL  (?) question
  2004-07-20 21:24 UTC  Mike Mascari <mascarm@mascari.com>
` SQL question
  2004-11-06 23:13 UTC  Uwe C. Schroeder <uwe@oss4u.com>
` Re: SQL question
  2004-11-07 01:17 UTC  Uwe C. Schroeder <uwe@oss4u.com>
` Re: SQL question
  2004-11-07 05:53 UTC  Vincent Hikida <vhikida@inreach.com>
` Re: SQL question
  2004-11-07 20:16 UTC  Greg Stark <gsstark@mit.edu>
` Re: SQL question
  2004-11-08 09:38 UTC  Uwe C. Schroeder <uwe@oss4u.com>
` sql question
  2005-03-11 12:26 UTC  Steven Verhoeven <Steven2@dmbr.ugent.be>
` sql question
  2005-03-11 12:36 UTC  Steven Verhoeven <Steven.Verhoeven@dmbr.UGent.be>
` Re: sql question
  2005-03-14 02:34 UTC  Vincent Hikida <vhikida@inreach.com>
` Re: sql question
  2005-03-14 02:39 UTC  Russell Smith <mr-russ@pws.com.au>
` Re: [NOVICE] sql question
  2005-03-14 02:42 UTC  Vincent Hikida <vhikida@inreach.com>
` Re: sql question
  2005-03-14 02:44 UTC  Klint Gore <kg@kgb.une.edu.au>
` Re: sql question
  2005-03-14 05:13 UTC  George Essig <george.essig@gmail.com>
` Re: sql question
  2005-03-14 08:41 UTC  Ragnar Hafstað <gnari@simnet.is>
` Re: sql question
  2005-03-14 17:50 UTC  Chris Travers <chris@travelamericas.com>
` SQL Question
  2005-04-15 11:58 UTC  Alex <alex@meerkatsoft.com>
` Re: SQL Question
  2005-04-15 12:15 UTC  Thomas Kellerer <spam_eater@gmx.net>
` Re: SQL Question
  2005-04-15 12:23 UTC  GIROIRE, Nicolas (COFRAMI) <nicolas.giroire@airbus.com>
` Re: SQL Question
  2005-04-15 13:41 UTC  Richard Huxton <dev@archonet.com>
` Re: SQL Question
  2005-04-15 13:56 UTC  GIROIRE, Nicolas (COFRAMI) <nicolas.giroire@airbus.com>
` Re: SQL Question
  2005-04-15 14:42 UTC  jday@gisolutions.us
` Re: SQL Question
  2005-04-15 15:47 UTC  Thomas Kellerer <spam_eater@gmx.net>
` Re: SQL Question
  2005-04-15 23:05 UTC  Bruno Wolff III <bruno@wolff.to>
` Re: SQL Question
  2005-04-16 08:10 UTC  Julian Scarfe <julian@avbrief.com>
` Re: SQL Question
  2005-04-17 12:53 UTC  Alex <alex@meerkatsoft.com>
` SQL question.
  2005-06-01 14:40 UTC  FC <lne-1mc8@myamail.com>
` Re: SQL question.
  2005-06-01 15:20 UTC  Jim Buttafuoco <jim@contactbda.com>
` Re: SQL question.
  2005-06-01 15:32 UTC  Martijn van Oosterhout <kleptog@svana.org>
` Re: SQL question.
  2005-06-01 15:49 UTC  FC <lne-1mc8@myamail.com>
` SQL question
  2008-03-29 04:59 UTC  kevin kempter <kevin@kevinkempterllc.com>
` Re: SQL question
  2008-03-29 05:03 UTC  Adam Rich <adam.r@sbcglobal.net>
` SQL Question
  2014-04-01 20:21 UTC  Robert DiFalco <robert.difalco@gmail.com>
` Re: SQL Question
  2014-04-01 20:27 UTC  Robert DiFalco <robert.difalco@gmail.com>
` Re: SQL Question
  2014-04-01 20:38 UTC  Paul Jungwirth <pj@illuminatedcomputing.com>
` Re: SQL Question
  2014-04-01 20:56 UTC  John R Pierce <pierce@hogranch.com>
` SQL question
  2023-01-14 16:32 UTC  hamann.w@t-online.de
  [71+ messages in thread]

Intervals and ISO 8601 duration
  2023-01-12 13:40 UTC  Sebastien Flaesch <sebastien.flaesch@4js.com>
` Re: Intervals and ISO 8601 duration
  2023-01-12 15:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Intervals and ISO 8601 duration
  2023-01-13 22:17 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 22:41 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 22:47 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 22:49 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 22:51 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 23:03 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 23:32 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 23:44 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-13 23:57 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 00:02 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 00:03 UTC  Bryn Llewellyn <bryn@yugabyte.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 00:07 UTC  Martin L. Buchanan <martinlbuchanan@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 00:08 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 00:28 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 00:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Intervals and ISO 8601 duration
  2023-01-14 01:24 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 02:16 UTC  Tatsuo Ishii <ishii@sraoss.co.jp>
` Re: Intervals and ISO 8601 duration
  2023-01-14 05:20 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Intervals and ISO 8601 duration
  2023-01-14 05:27 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 05:32 UTC  Peter J. Holzer <hjp-pgsql@hjp.at>
` Re: Intervals and ISO 8601 duration
  2023-01-14 06:01 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: Intervals and ISO 8601 duration
  2023-01-14 06:17 UTC  Ken Tanzer <ken.tanzer@gmail.com>
  [24+ messages in thread]

Dump (was: Intervals and ISO 8601 duration)
  2023-01-14 05:50 UTC  Peter J. Holzer <hjp-pgsql@hjp.at>

Directly embedding a psql SET variable inside another string?
  2023-01-13 16:12 UTC  Ron <ronljohnsonjr@gmail.com>
` Re: Directly embedding a psql SET variable inside another string?
  2023-01-13 17:08 UTC  Adam Scott <adam.c.scott@gmail.com>
` Re: Directly embedding a psql SET variable inside another string?
  2023-01-13 17:13 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Directly embedding a psql SET variable inside another string?
  2023-01-13 17:13 UTC  Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Directly embedding a psql SET variable inside another string?
  2023-01-13 17:14 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Directly embedding a psql SET variable inside another string?
  2023-01-13 18:07 UTC  Ron <ronljohnsonjr@gmail.com>
  [6+ 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