pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17553: Unreleased file resources exist
  2022-07-18 06:55 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #17483: postgres_fdw used with text to_tsvector and custom search configuration
  2022-05-16 09:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17483: postgres_fdw used with text to_tsvector and custom search configuration
  2022-05-16 14:49 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17483: postgres_fdw used with text to_tsvector and custom search configuration
  2022-07-17 22:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
  2022-07-15 23:37 UTC  Walker Philips <wphilips53@gmail.com>
` Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
  2022-07-16 00:41 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
  2022-07-16 00:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
  2022-07-16 00:54 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
  2022-07-16 21:20 UTC  Walker Philips <wphilips53@gmail.com>
` Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
  2022-07-16 23:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

Makefile.global will override configure parameters if "pgsql" and "postgres" appear anywhere in the source path name
  2022-07-15 16:13 UTC  Andy Bailey <bailey@akamai.com>
` Re: Makefile.global will override configure parameters if "pgsql" and "postgres" appear anywhere in the source path name
  2022-07-15 18:38 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Makefile.global will override configure parameters if "pgsql" and "postgres" appear anywhere in the source path name
  2022-07-15 20:25 UTC  Andres Freund <andres@anarazel.de>
` Re: Makefile.global will override configure parameters if "pgsql" and "postgres" appear anywhere in the source path name
  2022-07-15 23:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Makefile.global will override configure parameters if "pgsql" and "postgres" appear anywhere in the source path name
  2022-07-15 23:30 UTC  Andres Freund <andres@anarazel.de>
  [5+ messages in thread]

Auto-vacuum timing out and preventing connections
  2022-06-27 20:38 UTC  David Johansen <davejohansen@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-06-28 04:42 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-06-28 17:24 UTC  David Johansen <davejohansen@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-06-28 19:31 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-06-28 20:05 UTC  David Johansen <davejohansen@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-06-30 02:22 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-07-02 03:11 UTC  Andres Freund <andres@anarazel.de>
` Re: Auto-vacuum timing out and preventing connections
  2022-07-02 04:34 UTC  David Johansen <davejohansen@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-07-04 04:29 UTC  Xiong He <iihero@qq.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-07-14 16:51 UTC  David Johansen <davejohansen@gmail.com>
` Re: Auto-vacuum timing out and preventing connections
  2022-07-15 03:42 UTC  Andres Freund <andres@anarazel.de>
` Re: Auto-vacuum timing out and preventing connections
  2022-07-15 04:22 UTC  David Johansen <davejohansen@gmail.com>
  [12+ messages in thread]

BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses
  2022-07-14 14:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses
  2022-07-14 16:51 UTC  Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses
  2022-07-14 18:02 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses
  2022-07-14 18:24 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #17549: wrong index scan plan with RLS
  2022-07-13 11:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17549: wrong index scan plan with RLS
  2022-07-13 14:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

pg_ctl cannot find postgresql.conf
  2022-07-13 09:45 UTC  Дмитрий Карасёв <karasev.dmitrii94@mail.ru>
` Re: pg_ctl cannot find postgresql.conf
  2022-07-13 12:28 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_ctl cannot find postgresql.conf
  2022-07-13 13:08 UTC  Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
  [3+ messages in thread]

can't drop table due to reference from orphaned temp function
  2022-02-18 07:27 UTC  Miles Delahunty <miles.delahunty@gmail.com>
` Re: can't drop table due to reference from orphaned temp function
  2022-02-19 18:00 UTC  Andres Freund <andres@anarazel.de>
` Re: can't drop table due to reference from orphaned temp function
  2022-02-19 21:31 UTC  Andres Freund <andres@anarazel.de>
` Re: can't drop table due to reference from orphaned temp function
  2022-02-21 18:36 UTC  Andres Freund <andres@anarazel.de>
` Re: can't drop table due to reference from orphaned temp function
  2022-07-12 14:13 UTC  Yura Sokolov <y.sokolov@postgrespro.ru>
` Re: can't drop table due to reference from orphaned temp function
  2022-07-12 19:24 UTC  Andres Freund <andres@anarazel.de>
` Re: can't drop table due to reference from orphaned temp function
  2022-07-13 09:16 UTC  Yura Sokolov <y.sokolov@postgrespro.ru>
  [7+ messages in thread]

BUG #17548: Aggregate queries on partitioned tables can cause OOM.
  2022-07-12 16:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17548: Aggregate queries on partitioned tables can cause OOM.
  2022-07-12 22:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

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]


[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