pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17844: Memory consumption for memoize node
2023-03-15 09:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17844: Memory consumption for memoize node
2023-03-18 00:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17844: Memory consumption for memoize node
2023-03-19 09:33 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17844: Memory consumption for memoize node
2023-03-20 03:10 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17844: Memory consumption for memoize node
2023-03-20 03:37 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17844: Memory consumption for memoize node
2023-03-20 06:23 UTC Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #17844: Memory consumption for memoize node
2023-03-20 20:36 UTC David Rowley <dgrowleyml@gmail.com>
[7+ messages in thread]
BUG #17846: pg_dump doesn't properly dump with paused WAL replay
2023-03-16 11:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17846: pg_dump doesn't properly dump with paused WAL replay
2023-03-16 15:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17846: pg_dump doesn't properly dump with paused WAL replay
2023-03-16 20:32 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17846: pg_dump doesn't properly dump with paused WAL replay
2023-03-20 15:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
About the function current_user
2023-03-20 07:01 UTC Xiong He <iihero@qq.com>
` Re: About the function current_user
2023-03-20 07:05 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: About the function current_user
2023-03-20 08:16 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: About the function current_user
2023-03-20 08:49 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: About the function current_user
2023-03-20 08:56 UTC Xiong He <iihero@qq.com>
` Re: About the function current_user
2023-03-20 09:35 UTC Xiong He <iihero@qq.com>
` Re: About the function current_user
2023-03-20 12:13 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: About the function current_user
2023-03-20 12:16 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: About the function current_user
2023-03-20 13:58 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
[9+ messages in thread]
BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-06 06:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-08 09:26 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-08 10:06 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-08 10:16 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-08 15:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-08 15:33 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-08 16:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-09 03:53 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-09 16:18 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-02-11 19:00 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-03-17 20:20 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-03-20 09:31 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17774: Assert triggered on brin_minmax_multi.c
2023-03-20 10:15 UTC Dmitry Dolgov <9erthalion6@gmail.com>
[13+ messages in thread]
BUG #17853: COLLATE does not work with numeric column references in ORDER BY
2023-03-18 22:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17853: COLLATE does not work with numeric column references in ORDER BY
2023-03-19 00:55 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #17853: COLLATE does not work with numeric column references in ORDER BY
2023-03-19 01:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17853: COLLATE does not work with numeric column references in ORDER BY
2023-03-19 01:27 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17853: COLLATE does not work with numeric column references in ORDER BY
2023-03-19 09:34 UTC Branko Radovanovic <branko.radovanovic.zg@gmail.com>
` Re: BUG #17853: COLLATE does not work with numeric column references in ORDER BY
2023-03-19 18:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #17845: insert into on conflict bug .
2023-03-16 10:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17845: insert into on conflict bug .
2023-03-16 12:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17845: insert into on conflict bug .
2023-03-16 13:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17845: insert into on conflict bug .
2023-03-16 14:28 UTC jian he <jian.universality@gmail.com>
` Re:Re: BUG #17845: insert into on conflict bug .
2023-03-17 02:34 UTC 德哥 <digoal@126.com>
` Re: Re: BUG #17845: insert into on conflict bug .
2023-03-17 06:19 UTC jian he <jian.universality@gmail.com>
` Re: BUG #17845: insert into on conflict bug .
2023-03-17 12:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17845: insert into on conflict bug .
2023-03-17 14:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17845: insert into on conflict bug .
2023-03-17 20:08 UTC Peter Geoghegan <pg@bowt.ie>
[9+ messages in thread]
BUG #17852: gdal34: RPM build broken for RHEL8 and RHEL9 since 2023.01.08
2023-03-17 16:18 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-09 09:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-09 16:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-11 06:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-11 17:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-12 21:19 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-12 21:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-14 11:13 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-16 18:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-17 03:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
2023-03-17 03:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
BUG #17850: could not load library "$libdir/postgis-2.4" could not load library "$libdir/rtpostgis-2.4":
2023-03-16 23:57 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17848: Deadlock when running ANALYZE on a table while REINDEX INDEX CONCURRENTLY is running
2023-03-16 19:47 UTC PG Bug reporting form <noreply@postgresql.org>
pg_read_server_files doesn't let me use pg_ls_dir() or pg_read_file?
2023-03-14 19:33 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: pg_read_server_files doesn't let me use pg_ls_dir() or pg_read_file?
2023-03-15 02:10 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: pg_read_server_files doesn't let me use pg_ls_dir() or pg_read_file?
2023-03-15 10:46 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: pg_read_server_files doesn't let me use pg_ls_dir() or pg_read_file?
2023-03-16 01:11 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: pg_read_server_files doesn't let me use pg_ls_dir() or pg_read_file?
2023-03-16 11:56 UTC hubert depesz lubaczewski <depesz@depesz.com>
[5+ messages in thread]
BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
2023-03-14 11:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
2023-03-14 14:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
2023-03-15 16:49 UTC Sébastien <bokanist@gmail.com>
` Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
2023-03-15 19:33 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
2023-03-15 22:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
2023-03-16 07:40 UTC Sébastien <bokanist@gmail.com>
[6+ messages in thread]
Certificate expired
2023-03-15 17:42 UTC Sylvie Greverend <SGreverend@harriscomputer.com>
` Re: Certificate expired
2023-03-15 18:52 UTC Magnus Hagander <magnus@hagander.net>
` Re:Certificate expired
2023-03-15 19:00 UTC Sergei Kornilov <sk@zsrv.org>
[3+ messages in thread]
Merge command is erroring with: PlaceHolderVar found where not expected
2023-03-15 12:24 UTC Önder Kalacı <onderkalaci@gmail.com>
` Re: Merge command is erroring with: PlaceHolderVar found where not expected
2023-03-15 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-14 01:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-14 22:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-15 01:17 UTC Thiago Nunes <thiagotnunes@gmail.com>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-15 01:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-15 02:02 UTC Thiago Nunes <thiagotnunes@gmail.com>
[5+ messages in thread]
BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 15:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 16:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 18:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 18:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 19:26 UTC David G. Johnston <david.g.johnston@gmail.com>
[5+ messages in thread]
AW: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 18:12 UTC Hans Buschmann <buschmann@nidsa.net>
` AW: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 19:07 UTC Hans Buschmann <buschmann@nidsa.net>
[2+ messages in thread]
BUG #17843: Writing uninitialised data in logtape/buffile
2023-03-14 18:00 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17841: COPY Command Invalid QUOTES
2023-03-14 14:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17841: COPY Command Invalid QUOTES
2023-03-14 15:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
ERROR: PlaceHolderVar found where not expected
2023-03-14 03:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 03:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 03:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 06:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 15:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Invalid memory allocation error with pg_recvlogical or with libPQ logical connection
2023-03-13 07:01 UTC jitesh tiwari <jitesh120@gmail.com>
` Re: Invalid memory allocation error with pg_recvlogical or with libPQ logical connection
2023-03-13 11:43 UTC Arne Roland <A.Roland@index.de>
` Re: Invalid memory allocation error with pg_recvlogical or with libPQ logical connection
2023-03-14 06:07 UTC jitesh tiwari <jitesh120@gmail.com>
[3+ messages in thread]
BUG #17837: The potential risks associated with executing "commit" in a procedure.
2023-03-13 12:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17837: The potential risks associated with executing "commit" in a procedure.
2023-03-13 20:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17835: Two assertions failed in nodeAgg.c and execExprInterp.c with the same SQL
2023-03-13 02:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17835: Two assertions failed in nodeAgg.c and execExprInterp.c with the same SQL
2023-03-13 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17835: Two assertions failed in nodeAgg.c and execExprInterp.c with the same SQL
2023-03-13 16:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
disable pipeline mode
2023-03-13 08:44 UTC Oleksandr Volkovskyi <oleksandr.volkovskyi@modulrfinance.com>
` Re: disable pipeline mode
2023-03-13 15:49 UTC Daniel Verite <daniel@manitou-mail.org>
[2+ messages in thread]
BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 11:29 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 12:05 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 13:22 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 19:19 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-15 09:41 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-15 19:42 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-03-13 11:46 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[9+ 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