pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17544: Join order for INNER JOIN ... USING with GROUP BY on join column affects selected query plan
  2022-07-10 04:52 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17544: Join order for INNER JOIN ... USING with GROUP BY on join column affects selected query plan
  2022-07-12 06:34 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #17544: Join order for INNER JOIN ... USING with GROUP BY on join column affects selected query plan
  2022-07-12 17:52 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

Reducing chunk header sizes on all memory context types
  2022-07-12 04:57 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Reducing chunk header sizes on all memory context types
  2022-07-12 05:00 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

BUG #17546: power() function - value is distorted via automatic type cast
  2022-07-11 15:20 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17546: power() function - value is distorted via automatic type cast
  2022-07-11 15:49 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17546: power() function - value is distorted via automatic type cast
  2022-07-11 16:04 UTC  Антон Потапов <su.sinodan@gmail.com>
` Re: BUG #17546: power() function - value is distorted via automatic type cast
  2022-07-11 18:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #17542: tsquery returns incorrect results with nested, conjuncted followed-by operators
  2022-07-09 01:35 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17542: tsquery returns incorrect results with nested, conjuncted followed-by operators
  2022-07-11 12:34 UTC  Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17542: tsquery returns incorrect results with nested, conjuncted followed-by operators
  2022-07-11 13:18 UTC  Jordan Lewis <jordanthelewis@gmail.com>
  [3+ messages in thread]

pg_upgrade (12->14) fails on aggregate
  2022-05-04 13:05 UTC  Petr Vejsada <pve@paymorrow.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-05-04 14:34 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-14 23:09 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-15 19:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-17 02:01 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-17 13:07 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-17 13:30 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-17 14:14 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-22 23:58 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-24 18:43 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-24 20:28 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-25 10:34 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-27 23:30 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-29 17:58 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-29 18:07 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-06-29 18:43 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-07-05 17:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-07-06 01:50 UTC  Michael Paquier <michael@paquier.xyz>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-07-06 03:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade (12->14) fails on aggregate
  2022-07-07 05:04 UTC  Michael Paquier <michael@paquier.xyz>
  [20+ messages in thread]

Re: index cost estimation
  2022-07-06 14:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: index cost estimation
  2022-07-06 14:52 UTC  Ronan Dunklau <ronan.dunklau@aiven.io>
` Re: index cost estimation
  2022-07-06 15:42 UTC  Ronan Dunklau <ronan.dunklau@aiven.io>
  [3+ messages in thread]

[PATCH v1] Fix gin costing.
  2022-07-06 15:29 UTC  Ronan Dunklau <ronan.dunklau@aiven.io>

(no subject)
  2022-07-02 12:15 UTC  Hung Nguyen <hungnq1989@gmail.com>
` Re:
  2022-07-02 13:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re:
  2022-07-06 08:53 UTC  Ronan Dunklau <ronan.dunklau@aiven.io>
  [3+ messages in thread]

BUG #17539: Assert after CREATE OPERATOR CLASS command
  2022-07-05 20:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17539: Assert after CREATE OPERATOR CLASS command
  2022-07-05 20:36 UTC  Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #17539: Assert after CREATE OPERATOR CLASS command
  2022-07-05 22:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17539: Assert after CREATE OPERATOR CLASS command
  2022-07-06 03:41 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17539: Assert after CREATE OPERATOR CLASS command
  2022-07-06 03:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-08 13:59 UTC  Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-08 15:08 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-10 06:25 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-10 06:33 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-13 11:09 UTC  Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-13 14:54 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-15 18:26 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-15 18:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-16 01:34 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-16 01:41 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-16 03:07 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-17 18:31 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-21 02:42 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-21 05:56 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-21 05:59 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-21 06:05 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-21 08:46 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-06-29 12:09 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-07-04 08:27 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-07-04 08:49 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-07-04 09:32 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-07-05 12:39 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
  2022-07-06 01:05 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
  [23+ messages in thread]

PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-01 13:07 UTC  ROSESOFT S. Hoffmann <sh@rosesoft.de>
` Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-04 00:34 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-05 07:22 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-05 08:18 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-05 19:25 UTC  Thomas Munro <thomas.munro@gmail.com>
  [5+ messages in thread]

AW: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-04 11:53 UTC  ROSESOFT S. Hoffmann <sh@rosesoft.de>
` AW: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-05 13:29 UTC  ROSESOFT S. Hoffmann <sh@rosesoft.de>
  [2+ messages in thread]

BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-05-30 14:59 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-05-30 15:18 UTC  Christoph Berg <christoph.berg@credativ.de>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-05-31 02:39 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-02 05:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-03 08:56 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-06 02:15 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-06 06:11 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-06 14:30 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-06 20:05 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-07 02:53 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-10 15:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-10 16:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
`  Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-10 19:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-10 19:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
`  Re: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-11 07:35 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-13 06:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-13 07:07 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-13 14:52 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-14 01:31 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-06-15 06:09 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-07-04 14:38 UTC  Christoph Berg <christoph.berg@credativ.de>
` Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
  2022-07-05 00:12 UTC  Michael Paquier <michael@paquier.xyz>
  [22+ messages in thread]

BUG #17538: Dynamically updating log_hostname not affect the disconnection log
  2022-07-03 11:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17538: Dynamically updating log_hostname not affect the disconnection log
  2022-07-04 17:23 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #17537: Dynamically updating statement_timeout not affect the insert query right now.
  2022-07-03 05:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17537: Dynamically updating statement_timeout not affect the insert query right now.
  2022-07-03 15:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17537: Dynamically updating statement_timeout not affect the insert query right now.
  2022-07-03 15:09 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [3+ messages in thread]

Re: your mail
  2017-08-08 20:18 UTC  Andres Freund <andres@anarazel.de>
` Re: your mail
  2017-08-08 21:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: your mail
  2017-08-08 21:19 UTC  Andres Freund <andres@anarazel.de>
` Re: your mail
  2017-08-08 22:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: your mail
  2022-07-02 13:49 UTC  Julien Rouhaud <rjuju123@gmail.com>
  [5+ messages in thread]

pg15 beta2 bug:cause by logcial replation
  2022-07-01 03:35 UTC  396934406@qq.com <396934406@qq.com>
` RE: pg15 beta2 bug:cause by logcial replation
  2022-07-01 04:09 UTC  houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: pg15 beta2 bug:cause by logcial replation
  2022-07-01 05:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: RE: pg15 beta2 bug:cause by logcial replation
  2022-07-01 06:36 UTC  396934406@qq.com <396934406@qq.com>
` Re: Re: pg15 beta2 bug:cause by logcial replation
  2022-07-01 06:43 UTC  396934406@qq.com <396934406@qq.com>
` RE: RE: pg15 beta2 bug:cause by logcial replation
  2022-07-01 07:26 UTC  houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: RE: pg15 beta2 bug:cause by logcial replation
  2022-07-01 08:10 UTC  396934406@qq.com <396934406@qq.com>
` Re: RE: pg15 beta2 bug:cause by logcial replation
  2022-07-02 00:29 UTC  396934406@qq.com <396934406@qq.com>
  [8+ messages in thread]

[PATCH v8] libpq: Improve idle state handling in pipeline mode
  2022-07-01 16:11 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>

BUG #17535: postgresql-14-orafce 3.22.0-1.pgdg110+1 fails; 3.21.1-1.pgdg110+1 works.
  2022-07-01 14:21 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17535: postgresql-14-orafce 3.22.0-1.pgdg110+1 fails; 3.21.1-1.pgdg110+1 works.
  2022-07-01 16:05 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [2+ messages in thread]

BUG #17536: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-01 14:36 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17536: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
  2022-07-01 14:48 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
  2022-06-14 15:17 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
  2022-06-25 23:15 UTC  Dave Cramer <davecramer@postgres.rocks>
` Re: BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
  2022-06-25 23:51 UTC  David G. Johnston <david.g.johnston@gmail.com>
` RE: BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
  2022-06-27 16:36 UTC  Krier, Bob <rkrier@cleo.com>
` Re: BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
  2022-06-27 17:11 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
  2022-06-28 19:33 UTC  Dave Cramer <davecramer@postgres.rocks>
  [6+ messages in thread]

BUG #17534: 'tablespace' option crushes 'create database' query with 'permission denied' message
  2022-06-28 08:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17534: 'tablespace' option crushes 'create database' query with 'permission denied' message
  2022-06-28 18:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

[PATCH v7 6/6] Add the CLOSE message fix
  2022-06-26 17:53 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>

BUG #17532: Prepared statements and insert on conflict can fail on the 6th execution
  2022-06-25 15:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17532: Prepared statements and insert on conflict can fail on the 6th execution
  2022-06-25 15:56 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

[PATCH v7 5/6] add PIPELINE_IDLE state
  2022-06-24 16:13 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>


[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