pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedAW: BUG #18725: "set role" requires "grant connect on database"
2024-12-03 12:36 UTC PostgreSQL TDBA (LDBV) <PostgreSQL_TDBA@ldbv.bayern.de>
BUG #18707: Installation issue
2024-11-14 08:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18707: Installation issue
2024-11-18 09:21 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` RE: [EXTERNAL] Re: BUG #18707: Installation issue
2024-11-18 10:30 UTC PANESAR Gursharan <gursharan.panesar@bnpparibas.com>
` Re: [EXTERNAL] Re: BUG #18707: Installation issue
2024-11-18 11:06 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: [EXTERNAL] Re: BUG #18707: Installation issue
2024-11-19 01:09 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: [EXTERNAL] Re: BUG #18707: Installation issue
2024-11-19 07:01 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: [EXTERNAL] Re: BUG #18707: Installation issue
2024-11-19 23:15 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: [EXTERNAL] Re: BUG #18707: Installation issue
2024-11-20 22:41 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18707: Installation issue
2024-12-03 06:03 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[9+ messages in thread]
BUG #18729: update with multiple subpartitions return error: too many range table entries
2024-12-02 07:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18729: update with multiple subpartitions return error: too many range table entries
2024-12-02 15:37 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks
2024-11-27 18:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks
2024-11-28 11:27 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks
2024-12-02 08:36 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
[3+ messages in thread]
回复：BUG #18729: update with multiple subpartitions return error: too many range table entries
2024-12-02 07:10 UTC 飞鱼 <303677365@qq.com>
encrypted pk8 keys work with libpg connection but not in postgres_fdw
2024-07-10 15:11 UTC Hunter Payne <huntercpayne@proton.me>
` Re: encrypted pk8 keys work with libpg connection but not in postgres_fdw
2024-12-01 14:25 UTC Dave Cramer <davecramer@postgres.rocks>
[2+ messages in thread]
Bug report for plpgsql
2024-11-28 23:29 UTC Slivaev Dmitry <dmitry.slivaev@gmail.com>
` Re: Bug report for plpgsql
2024-11-29 15:41 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug report for plpgsql
2024-11-29 15:48 UTC Pavel Stehule <pavel.stehule@gmail.com>
[3+ messages in thread]
BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12.
2024-11-27 16:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12.
2024-11-27 17:54 UTC Erik Wienhold <ewie@ewie.name>
` Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12.
2024-11-28 13:22 UTC Zaid Shabbir <zaidshabbir@gmail.com>
[3+ messages in thread]
Dropping partition with CASCADE drops constraints on partitioned table
2024-11-28 12:03 UTC Vladyslav Hutych <vladyslav.hutych@ipfabric.io>
Detection of hadware feature => please do not use signal
2024-10-31 15:41 UTC Bastien Roucariès <rouca@debian.org>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 17:29 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 17:42 UTC Bastien Roucariès <rouca@debian.org>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 17:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 18:01 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 18:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 20:12 UTC Bastien Roucariès <rouca@debian.org>
` Re: Detection of hadware feature => please do not use signal
2024-10-31 20:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-01 04:28 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-01 04:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-01 06:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-01 10:20 UTC Bastien Roucariès <rouca@debian.org>
` Re: Detection of hadware feature => please do not use signal
2024-11-02 05:11 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-07 00:01 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-07 15:28 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-07 15:51 UTC Bastien Roucariès <rouca@debian.org>
` Re: Detection of hadware feature => please do not use signal
2024-11-07 23:43 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-08 08:56 UTC Bastien Roucariès <rouca@debian.org>
` Re: Detection of hadware feature => please do not use signal
2024-11-10 09:19 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-22 10:11 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-23 01:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-23 05:10 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-23 05:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-23 22:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-23 23:50 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-24 00:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-24 19:07 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-24 20:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-24 22:50 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-24 23:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-25 00:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-25 00:47 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Detection of hadware feature => please do not use signal
2024-11-25 01:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-25 15:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-25 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-25 22:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Detection of hadware feature => please do not use signal
2024-11-27 19:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[37+ messages in thread]
BUG #18725: "set role" requires "grant connect on database"
2024-11-27 15:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18725: "set role" requires "grant connect on database"
2024-11-27 18:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
[PATCH v8 1/1] fix database name truncation
2024-11-27 15:19 UTC Nathan Bossart <nathan@postgresql.org>
Function pg_get_constraintdef
2024-11-21 11:46 UTC Erki Eessaar <erki.eessaar@taltech.ee>
` Re: Function pg_get_constraintdef
2024-11-21 12:04 UTC Erki Eessaar <erki.eessaar@taltech.ee>
` Re: Function pg_get_constraintdef
2024-11-21 12:16 UTC Magnus Hagander <magnus@hagander.net>
` Re: Function pg_get_constraintdef
2024-11-21 12:30 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Function pg_get_constraintdef
2024-11-21 12:43 UTC Magnus Hagander <magnus@hagander.net>
` Re: Function pg_get_constraintdef
2024-11-27 12:53 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[6+ messages in thread]
BUG #18724: High data disk utilization during log writing
2024-11-25 12:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18724: High data disk utilization during log writing
2024-11-25 14:47 UTC Christophe Pettus <xof@thebuild.com>
` Re: BUG #18724: High data disk utilization during log writing
2024-11-26 10:33 UTC Иван Ситников <sit7602@gmail.com>
[3+ messages in thread]
'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
2024-11-20 05:11 UTC Aya Iwata (Fujitsu) <iwata.aya@fujitsu.com>
` Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
2024-11-20 06:27 UTC Noah Misch <noah@leadboat.com>
` Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
2024-11-21 01:11 UTC Noah Misch <noah@leadboat.com>
` RE: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
2024-11-25 05:54 UTC Aya Iwata (Fujitsu) <iwata.aya@fujitsu.com>
` Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
2024-11-26 02:17 UTC Noah Misch <noah@leadboat.com>
[5+ messages in thread]
BUG #18722: Processing arrays with plpgsql raises errors
2024-11-23 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-24 01:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-24 22:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-25 10:30 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-25 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-25 17:59 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-25 19:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18722: Processing arrays with plpgsql raises errors
2024-11-25 20:42 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[8+ messages in thread]
[PATCH] Avoid usage of freed memory in parallel_vacuum_reset_dead_items
2024-11-25 17:26 UTC Vallimaharajan <vallimaharajan.gs@zohocorp.com>
Today's Postgres Releases break login roles
2024-11-15 14:47 UTC Etienne LAFARGE <etienne.lafarge@gmail.com>
` Re: Today's Postgres Releases break login roles
2024-11-15 23:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Today's Postgres Releases break login roles
2024-11-16 04:53 UTC Noah Misch <noah@leadboat.com>
` Re: Today's Postgres Releases break login roles
2024-11-16 10:45 UTC Matthew Woodcraft <matthew@woodcraft.me.uk>
` Re: Today's Postgres Releases break login roles
2024-11-16 15:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Today's Postgres Releases break login roles
2024-11-16 18:34 UTC Noah Misch <noah@leadboat.com>
` Re: Today's Postgres Releases break login roles
2024-11-16 20:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Today's Postgres Releases break login roles
2024-11-20 13:30 UTC Etienne LAFARGE <etienne.lafarge@gmail.com>
` Re: Today's Postgres Releases break login roles
2024-11-25 03:42 UTC Noah Misch <noah@leadboat.com>
[9+ messages in thread]
Can not open Postgre SQL 17.1 after update
2024-11-20 11:16 UTC Большой Сэм <samattreasure@gmail.com>
` Re: Can not open Postgre SQL 17.1 after update
2024-11-21 00:42 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Can not open Postgre SQL 17.1 after update
2024-11-24 15:55 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[3+ messages in thread]
Vacuum full failing xmin check, but vacuum freeze ok on v16
2024-11-23 15:06 UTC Greg Sabino Mullane <htamfids@gmail.com>
BUG #18721: Documentation for psql does not specify that the history feature doesn't work
2024-11-23 03:45 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18720: Can not install
2024-11-23 00:52 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
2024-09-11 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
2024-09-11 09:55 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
2024-09-12 02:30 UTC a.kozhemyakin <a.kozhemyakin@postgrespro.ru>
` Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
2024-09-12 22:33 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
2024-11-08 05:15 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
2024-11-22 02:51 UTC Thomas Munro <thomas.munro@gmail.com>
[6+ messages in thread]
AW: AW: Wrong german error message encoding
2024-11-21 15:11 UTC radagast42@gmx.net
AW: Wrong german error message encoding
2024-11-21 12:28 UTC radagast42@gmx.net
` Re: AW: Wrong german error message encoding
2024-11-21 14:53 UTC Erik Wienhold <ewie@ewie.name>
[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