pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18807: libcrypto.so.1.1: cannot open shared object file
2025-02-12 12:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18807: libcrypto.so.1.1: cannot open shared object file
2025-02-12 17:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Error for GRANTED BY in PG16&PG17 that does not happen in PG15
2025-02-12 10:56 UTC Floris Van Nee <florisvannee@Optiver.com>
[PATCH v1] BRIN: be stricter about required support procs
2025-02-12 10:55 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
BUG #18805: A specific query on a hash partitioned table always causes a "signal 11: Segmentation fault" error.
2025-02-12 03:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18805: A specific query on a hash partitioned table always causes a "signal 11: Segmentation fault" error.
2025-02-12 07:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Fwd: BUG #18805: A specific query on a hash partitioned table always causes a "signal 11: Segmentation fault" error.
2025-02-12 08:55 UTC weijie JL <weijie1006jl@gmail.com>
[3+ messages in thread]
BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1
2025-02-11 14:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1
2025-02-11 15:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1
2025-02-11 20:55 UTC Marko Tiikkaja <marko@joh.to>
[3+ messages in thread]
BUG #18802: password field in log
2025-02-11 08:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18802: password field in log
2025-02-11 08:30 UTC Robert Sjöblom <robert.sjoblom@fortnox.se>
[2+ messages in thread]
BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
2025-01-15 05:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
2025-01-15 13:32 UTC Daniel Gustafsson <daniel@yesql.se>
` BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
2025-02-10 04:09 UTC 濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>
` Re: BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
2025-02-10 04:18 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
2025-02-10 09:47 UTC 濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>
[5+ messages in thread]
BUG #18795: Norwegian bokmål crashes again
2025-02-05 07:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18795: Norwegian bokmål crashes again
2025-02-05 16:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18795: Norwegian bokmål crashes again
2025-02-05 16:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18795: Norwegian bokmål crashes again
2025-02-05 16:32 UTC Øystein Monsrud Arneson <oystein.arneson@cloudberries.no>
` Re: BUG #18795: Norwegian bokmål crashes again
2025-02-05 16:38 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: BUG #18795: Norwegian bokmål crashes again
2025-02-05 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18795: Norwegian bokmål crashes again
2025-02-10 03:21 UTC Thomas Munro <thomas.munro@gmail.com>
[7+ messages in thread]
BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-04 12:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-04 15:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-04 15:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-04 15:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-09 23:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-10 00:55 UTC David G. Johnston <david.g.johnston@gmail.com>
[6+ messages in thread]
Ynt: Ynt: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-10 00:21 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
Ynt: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-09 21:22 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
` Ynt: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-09 22:34 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
` Re: Ynt: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
2025-02-09 23:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18800: Error while using pg_combinebackup
2025-02-07 23:30 UTC PG Bug reporting form <noreply@postgresql.org>
Bug in recovery of drop database?
2025-02-05 20:24 UTC David Steele <david@pgbackrest.org>
` Re: Bug in recovery of drop database?
2025-02-06 15:55 UTC David Steele <david@pgbackrest.org>
` Re: Bug in recovery of drop database?
2025-02-06 18:05 UTC Andres Freund <andres@anarazel.de>
` Re: Bug in recovery of drop database?
2025-02-06 19:28 UTC David Steele <david@pgbackrest.org>
` Re: Bug in recovery of drop database?
2025-02-07 14:16 UTC David Steele <david@pgbackrest.org>
[5+ messages in thread]
BUG #18799: /src/interfaces/ecpg/pgtypeslib/timestamp.c possible NULL deref
2025-02-06 11:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18799: /src/interfaces/ecpg/pgtypeslib/timestamp.c possible NULL deref
2025-02-06 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18797: pointer te->defn not checked for NULL
2025-02-06 11:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18797: pointer te->defn not checked for NULL
2025-02-06 15:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18794: pgBouncer Windows installation error due to a simple sql bug???
2025-02-05 00:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18794: pgBouncer Windows installation error due to a simple sql bug???
2025-02-06 13:17 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[2+ messages in thread]
pg_get_constraintdef throws SQL Error [XX000]: ERROR: invalid constraint type "n" (PG17)
2025-02-06 10:10 UTC Pierre-Paul Hackens <pierre-paul@geopostcodes.com>
` Re: pg_get_constraintdef throws SQL Error [XX000]: ERROR: invalid constraint type "n" (PG17)
2025-02-06 12:32 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
BUG #18798: /src/interfaces/ecpg/preproc/type.c possible NULL deref
2025-02-06 11:43 UTC PG Bug reporting form <noreply@postgresql.org>
Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-02 11:24 UTC Mor Lehr <mor.lehr@deel.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-02 15:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-02 15:26 UTC Mor Lehr <mor.lehr@deel.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-02 15:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-02 15:42 UTC Mor Lehr <mor.lehr@deel.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-02 22:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-03 16:45 UTC Erik Wienhold <ewie@ewie.name>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-03 18:11 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-04 06:39 UTC Mor Lehr <mor.lehr@deel.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-10 11:56 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2024-06-10 15:00 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2025-02-06 06:47 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
2025-02-06 10:10 UTC Mor Lehr <mor.lehr@deel.com>
[13+ messages in thread]
Bug in psql
2025-01-29 22:56 UTC Chris BSomething <xpusostomos@gmail.com>
` Re: Bug in psql
2025-01-30 07:54 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Bug in psql
2025-02-02 19:48 UTC Chris BSomething <xpusostomos@gmail.com>
` Re: Bug in psql
2025-02-02 20:35 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in psql
2025-02-03 00:29 UTC Chris BSomething <xpusostomos@gmail.com>
` Re: Bug in psql
2025-02-03 02:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in psql
2025-02-03 02:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug in psql
2025-02-03 12:29 UTC Chris BSomething <xpusostomos@gmail.com>
` Re: Bug in psql
2025-02-03 13:19 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Bug in psql
2025-02-03 16:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug in psql
2025-02-03 19:58 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Bug in psql
2025-02-05 16:31 UTC Chris BSomething <xpusostomos@gmail.com>
` Re: Bug in psql
2025-02-05 20:08 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Bug in psql
2025-02-06 03:10 UTC Chris BSomething <xpusostomos@gmail.com>
[14+ messages in thread]
BUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations
2025-02-05 20:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations
2025-02-06 00:06 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
bug report: initdb failure on Microsoft Windows if path to initdb contains special chars
2025-02-04 13:57 UTC Stöcker Bernhard - aktivweb GmbH <bernhard.stoecker@aktivweb.de>
` Re: bug report: initdb failure on Microsoft Windows if path to initdb contains special chars
2025-02-04 15:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 19:19 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 19:24 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 20:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 20:46 UTC Basha <basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 21:18 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 21:24 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 23:44 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 00:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 00:29 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 00:32 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:03 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:30 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:40 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:48 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 02:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 02:19 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 02:27 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 14:09 UTC Joe Conway <mail@joeconway.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 14:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 15:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 15:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 16:03 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 17:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 17:29 UTC Christophe Pettus <xof@thebuild.com>
` RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 17:51 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 18:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 18:57 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-09 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2025-02-04 14:43 UTC Georgy Artos <georgyartos@gmail.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2025-02-04 14:53 UTC Daniel Gustafsson <daniel@yesql.se>
[30+ messages in thread]
BUG #18789: logical replication slots are deleted after failovers
2025-01-29 12:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18789: logical replication slots are deleted after failovers
2025-01-29 19:13 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: BUG #18789: logical replication slots are deleted after failovers
2025-01-30 11:48 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18789: logical replication slots are deleted after failovers
2025-02-01 05:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18789: logical replication slots are deleted after failovers
2025-02-03 13:59 UTC Sachin Konde-Deshmukh <sachinkonde3@gmail.com>
` RE: BUG #18789: logical replication slots are deleted after failovers
2025-02-04 04:20 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[6+ messages in thread]
BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
2025-02-03 17:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
2025-02-03 23:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ 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