Mailing lists [pgsql-bugs]
- Re: Detection of hadware feature => please do not use signal Heikki Linnakangas
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically. Tyler
- Re: Detection of hadware feature => please do not use signal Tom Lane
- BUG #18682: Null grouping set with empty table returns a row contains null. PG Bug reporting form
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically. Laurenz Albe
- Re: BUG #17284: Assert failed in SerialAdd() when the summarize_serial mode is engaged Heikki Linnakangas
- Re: Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically. David Rowley
- Re: BUG #18682: Null grouping set with empty table returns a row contains null. Tom Lane
- BUG #18683: A publication must be created *before* a logical rep slot in order to be used with that slot? PG Bug reporting form
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- BUG #18684: script give me incorrect link to postgres PG Bug reporting form
- BUG #18685: .pgpass is not enabled when running pg_basebackup on PostgreSQL 17. PG Bug reporting form
- Re: BUG #18683: A publication must be created *before* a logical rep slot in order to be used with that slot? Peter Eisentraut
- Re: BUG #18685: .pgpass is not enabled when running pg_basebackup on PostgreSQL 17. Greg Sabino Mullane
- Re: BUG #18685: .pgpass is not enabled when running pg_basebackup on PostgreSQL 17. Tom Lane
- Re: BUG #18568: BUG: Result wrong when do group by on partition table! Amit Langote
- BUG #18688: _LSOpenURLsWithCompletionHandler() failed with error -54. (1) PG Bug reporting form
- BUG #18689: psql : operator "!=" do not behave like "<>" PG Bug reporting form
- Re: BUG #18688: _LSOpenURLsWithCompletionHandler() failed with error -54. (1) Daniel Gustafsson
- Re: BUG #18689: psql : operator "!=" do not behave like "<>" Rafia Sabih
- Re: BUG #18689: psql : operator "!=" do not behave like "<>" Tom Lane
- Re: BUG #18689: psql : operator "!=" do not behave like "<>" Erik Wienhold
- BUG #18685: -> Does the similar bug affect executable "pg_dump" too in Ver 17.0 Bharani SV-forum
- Re: BUG #18685: -> Does the similar bug affect executable "pg_dump" too in Ver 17.0 Laurenz Albe
- Re: BUG #18655: APT repository shell script doesn't work Christoph Berg
- Re: BUG #18655: APT repository shell script doesn't work William Chipman
- Re: BUG #18655: APT repository shell script doesn't work Christoph Berg
- Re: HashAgg degenerate case David Rowley
- BUG #18690: A count function returns wrong value when using FDW PG Bug reporting form
- Re: BUG #18683: A publication must be created *before* a logical rep slot in order to be used with that slot? Amit Kapila
- Re: BUG #18690: A count function returns wrong value when using FDW David Rowley
- BUG #18691: Turkish Character Encoding PG Bug reporting form
- BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length PG Bug reporting form
- Re: BUG #18690: A count function returns wrong value when using FDW Aidar Uldanov
- Re: BUG #18690: A count function returns wrong value when using FDW Aidar Uldanov
- Re: BUG #18690: A count function returns wrong value when using FDW Tom Lane
- Re: BUG #18690: A count function returns wrong value when using FDW Aidar Uldanov
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Tom Lane
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Alexander Korotkov
- BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type PG Bug reporting form
- Re: BUG #18691: Turkish Character Encoding Thomas Munro
- Re: BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type Tom Lane
- Re: BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type Jan Behrens
- TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Aleksander Alekseev
- BUG #18694: DISCARD ALL does not reset execution counters for plpgsql functions PG Bug reporting form
- BUG #18696: Compatibility Query for Updating zlib1.dll in PostgreSQL 10.2 to Address Security Vulnerabilities PG Bug reporting form
- Re: BUG #18694: DISCARD ALL does not reset execution counters for plpgsql functions David G. Johnston
- Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Tom Lane
- Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Aleksander Alekseev
- Re: Detection of hadware feature => please do not use signal Nathan Bossart
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Tom Lane
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Noah Misch
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Tom Lane
- Suboptimal query plans for BETWEEN SYMMETRIC operations Mineharu Takahara
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Noah Misch
- Re: Suboptimal query plans for BETWEEN SYMMETRIC operations David Rowley
- Re: Suboptimal query plans for BETWEEN SYMMETRIC operations Tom Lane
- Re: pg_rewind fails on Windows where tablespaces are used Andrew Dunstan
- Re: Suboptimal query plans for BETWEEN SYMMETRIC operations Mineharu Takahara
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Tom Lane
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Tender Wang
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Tom Lane
- Re: BUG #18694: DISCARD ALL does not reset execution counters for plpgsql functions David Pavlíček
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Alexander Korotkov
- Re: BUG #18568: BUG: Result wrong when do group by on partition table! Amit Langote
- Re: BUG #18568: BUG: Result wrong when do group by on partition table! Tender Wang
- Re: BUG #18694: DISCARD ALL does not reset execution counters for plpgsql functions Pavel Stehule
- BUG #18697: Postgresql does not start PG Bug reporting form
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Tom Lane
- Re: HashAgg degenerate case Andres Freund
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Tom Lane
- Segmentation fault - PostgreSQL 17.0 Ľuboslav Špilák
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Noah Misch
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Tom Lane
- Re: HashAgg degenerate case Jeff Davis
- Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length Alexander Korotkov
- Re: HashAgg degenerate case Jeff Davis
- Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start Noah Misch
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- Re: Segmentation fault - PostgreSQL 17.0 Ľuboslav Špilák
- Re: Segmentation fault - PostgreSQL 17.0 Peter Geoghegan
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- Re: Segmentation fault - PostgreSQL 17.0 Ľuboslav Špilák
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- BUG #18698: Checksum verification failed for: deb_postgis_3_4_pg16.app.zip PG Bug reporting form
- BUG #18699: Checksum verification failed for: edb_pgagent_pg17.app.zip PG Bug reporting form
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- Re: Segmentation fault - PostgreSQL 17.0 Tomas Vondra
- BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration) PG Bug reporting form
- RE: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607 Haifang Wang (Centific Technologies Inc)
- Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607 Thomas Munro
- RE: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607 Haifang Wang (Centific Technologies Inc)
- BUG #18701: Read of Bounds - elog.c PG Bug reporting form
- BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16 PG Bug reporting form
- Re: BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16 David G. Johnston
- Re: BUG #18675: Postgres is not realasing memory causing OOM Daniel Gustafsson
- Re: BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration) Tom Lane
- Re: HashAgg degenerate case Andres Freund
- Very long loop breaking logical replication walsender / walreceiver connection RECHTÉ Marc
- Re: BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16 Daniel Gustafsson
- Re: BUG #18699: Checksum verification failed for: edb_pgagent_pg17.app.zip Daniel Gustafsson
- Re: BUG #18699: Checksum verification failed for: edb_pgagent_pg17.app.zip Kritika Agarwal
- BUG #18704: Installing postgis fails due to depencies PG Bug reporting form
- Regression from postgresql14 to postgresql17 with postgis (osm2pgsql) Elie Gedeon
- BUG #18705: Segmentation fault when create brin index on user-defined type. PG Bug reporting form
- BUG #18707: Installation issue PG Bug reporting form
- Export PostgreSQL database into mysql database Chirag Patel
- BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" PG Bug reporting form
- Sorting Discrepancy in PostgreSQL 14.13 [3반]김민지_4904
- Re: BUG #18705: Segmentation fault when create brin index on user-defined type. Tomas Vondra
- Re: Libpq library error when doing physical Replication Aleksander Alekseev
- Re: Regression from postgresql14 to postgresql17 with postgis (osm2pgsql) Aleksander Alekseev
- Re: Regression from postgresql14 to postgresql17 with postgis (osm2pgsql) Aleksander Alekseev
- Re: Sorting Discrepancy in PostgreSQL 14.13 Tomas Vondra
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Aleksander Alekseev
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Aleksander Alekseev
- Re: Export PostgreSQL database into mysql database Greg Sabino Mullane
- BUG #18709: Explicit tablespace pg_default not working when creating of indices in partitioned tables PG Bug reporting form
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Robert Haas
- Re: Regression from postgresql14 to postgresql17 with postgis (osm2pgsql) Tomas Vondra
- Re: Libpq library error when doing physical Replication Danish Hajwane
- Re: Libpq library error when doing physical Replication Aleksander Alekseev
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- BUG #18710: "pg_get_viewdef" triggers assertions in special scenarios PG Bug reporting form
- Re: Sorting Discrepancy in PostgreSQL 14.13 Tom Lane
- Re: BUG #18705: Segmentation fault when create brin index on user-defined type. Tender Wang
- Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index Tender Wang
- Re:BUG #18710: "pg_get_viewdef" triggers assertions in special scenarios zengman
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Aleksander Alekseev
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Aleksander Alekseev
- Today's Postgres Releases break login roles Etienne LAFARGE
- Re: BUG #18705: Segmentation fault when create brin index on user-defined type. Tomas Vondra
- Re: BUG #18705: Segmentation fault when create brin index on user-defined type. Tom Lane
- Re: Today's Postgres Releases break login roles Tom Lane
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- BUG #18711: Attempting a connection with a database name longer than 63 characters now fails PG Bug reporting form
- Re: Libpq library error when doing physical Replication Danish Hajwane
- Re: Today's Postgres Releases break login roles Noah Misch
- BUG #18712: inet value ::2 handling goes not as expected PG Bug reporting form
- Re: Today's Postgres Releases break login roles Matthew Woodcraft
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Alexander Lakhin
- Re: Today's Postgres Releases break login roles Tom Lane
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- Re: Today's Postgres Releases break login roles Tom Lane
- Build failure with GCC 15 (defaults to -std=gnu23) Sam James
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Alexander Lakhin
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- ERROR: commutator operator - is already the commutator of operator + shohorab hossain
- Re: ERROR: commutator operator - is already the commutator of operator + Tom Lane
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Noah Misch
- Re: BUG #18712: inet value ::2 handling goes not as expected Tom Lane
- Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: BUG #18712: inet value ::2 handling goes not as expected Denis Feklushkin
- Getting error while building PSQL 17.1 on AIX box Raghu Dev Ramaiah
- Re: BUG #18707: Installation issue Sandeep Thakkar
- Re: Libpq library error when doing physical Replication Aleksander Alekseev
- Re: [EXTERNAL] Re: BUG #18707: Installation issue Sandeep Thakkar
- BUG #18713: pg_upgrade fails when owner of an extension is changed or dropped PG Bug reporting form
- Re: Getting error while building PSQL 17.1 on AIX box Tom Lane
- Re: BUG #18713: pg_upgrade fails when owner of an extension is changed or dropped Tom Lane
- Re: Getting error while building PSQL 17.1 on AIX box Rainer Tammer
- Re: Getting error while building PSQL 17.1 on AIX box Tom Lane
- Re: [EXTERNAL] - Re: Getting error while building PSQL 17.1 on AIX box Raghu Dev Ramaiah
- BUG #18714: error during installation PG Bug reporting form
- Re: BUG #18712: inet value ::2 handling goes not as expected Tom Lane
- BUG #18715: replace() function silently fails if 3rd argument is null PG Bug reporting form
- Re: [EXTERNAL] Re: BUG #18707: Installation issue Thomas Munro
- Re: BUG #18710: "pg_get_viewdef" triggers assertions in special scenarios zengman
- Re: BUG #18696: Compatibility Query for Updating zlib1.dll in PostgreSQL 10.2 to Address Security Vulnerabilities Bruce Momjian
- RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 Bing Xu
- Re: [EXTERNAL] Re: BUG #18707: Installation issue Sandeep Thakkar
- Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently Tender Wang
- Re: BUG #18715: replace() function silently fails if 3rd argument is null David G. Johnston
- Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 David G. Johnston
- Re: BUG #18696: Compatibility Query for Updating zlib1.dll in PostgreSQL 10.2 to Address Security Vulnerabilities Bruce Momjian
- Re: BUG #18715: replace() function silently fails if 3rd argument is null Chris BSomething
- Re: BUG #18715: replace() function silently fails if 3rd argument is null David G. Johnston
- Re: BUG #18715: replace() function silently fails if 3rd argument is null Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18715: replace() function silently fails if 3rd argument is null Erik Wienhold
- Re: BUG #18715: replace() function silently fails if 3rd argument is null Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: [EXTERNAL] Re: BUG #18707: Installation issue Thomas Munro
- Re: BUG #18715: replace() function silently fails if 3rd argument is null Erik Wienhold
- RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 Bing Xu
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 David G. Johnston
- RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 Bing Xu
- Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 David G. Johnston
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5 Aya Iwata (Fujitsu)
- BUG #18716: I wanted to upload/restore tar file data, While uploading file facing error, image attached. PG Bug reporting form
- Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5 Noah Misch
- Wrong german error message encoding
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Peter Eisentraut
- Re: Sorting Discrepancy in PostgreSQL 14.13 Peter Eisentraut
- Re: Wrong german error message encoding Daniel Gustafsson
- Can not open Postgre SQL 17.1 after update Большой Сэм
- BUG #18717: ALTER ROLE SET ROLE functionality is broken PG Bug reporting form
- Re: Today's Postgres Releases break login roles Etienne LAFARGE
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18717: ALTER ROLE SET ROLE functionality is broken Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Just tried to build Postgres 17 on AIX Mark Hill
- Re: Just tried to build Postgres 17 on AIX Heikki Linnakangas
- Re: [EXTERNAL] Re: BUG #18707: Installation issue Thomas Munro
- Re: Can not open Postgre SQL 17.1 after update Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Peter Eisentraut
- BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page PG Bug reporting form
- BUG #18719: Bug Report for Patch (For inplace update durability, make heap_update() callers wait) PG Bug reporting form
- Function pg_get_constraintdef Erki Eessaar
- Re: Function pg_get_constraintdef Erki Eessaar
- Re: Function pg_get_constraintdef Magnus Hagander
- AW: Wrong german error message encoding
- Re: BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page Alvaro Herrera
- Re: BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page Daniel Gustafsson
- Re: Function pg_get_constraintdef Magnus Hagander
- Re: BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page Magnus Hagander
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
- Re: BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page Daniel Gustafsson
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
- Re: AW: Wrong german error message encoding Erik Wienhold
- AW: AW: Wrong german error message encoding
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved Thomas Munro
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails John Naylor
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity Maxim Orlov
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- BUG #18720: Can not install PG Bug reporting form
- Re: Detection of hadware feature => please do not use signal Tom Lane
- BUG #18721: Documentation for psql does not specify that the history feature doesn't work PG Bug reporting form
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: Detection of hadware feature => please do not use signal Tom Lane
- BUG #18722: Processing arrays with plpgsql raises errors PG Bug reporting form
- Vacuum full failing xmin check, but vacuum freeze ok on v16 Greg Sabino Mullane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: BUG #18722: Processing arrays with plpgsql raises errors Tom Lane
- Re: Can not open Postgre SQL 17.1 after update Sandeep Thakkar
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: BUG #18722: Processing arrays with plpgsql raises errors Tom Lane
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Detection of hadware feature => please do not use signal Thomas Munro
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Today's Postgres Releases break login roles Noah Misch
- RE: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5 Aya Iwata (Fujitsu)
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: BUG #18722: Processing arrays with plpgsql raises errors Dean Rasheed
- BUG #18724: High data disk utilization during log writing PG Bug reporting form
- Re: BUG #18724: High data disk utilization during log writing Christophe Pettus
- Re: BUG #18722: Processing arrays with plpgsql raises errors Tom Lane
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Peter Eisentraut
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: BUG #18722: Processing arrays with plpgsql raises errors Dean Rasheed
- Re: BUG #18722: Processing arrays with plpgsql raises errors Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: BUG #18722: Processing arrays with plpgsql raises errors Dean Rasheed
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5 Noah Misch
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: BUG #18724: High data disk utilization during log writing Иван Ситников
- Re: pg_rewind fails on Windows where tablespaces are used Thomas Munro
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
- Re: pg_rewind fails on Windows where tablespaces are used Andrew Dunstan
- Re: Function pg_get_constraintdef Alvaro Herrera
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- BUG #18725: "set role" requires "grant connect on database" PG Bug reporting form
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12. PG Bug reporting form
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12. Erik Wienhold
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: BUG #18725: "set role" requires "grant connect on database" Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
- BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks PG Bug reporting form
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Andres Freund
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Sam James
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Andres Freund
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Andres Freund
- Re: Detection of hadware feature => please do not use signal Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks Bertrand Drouvot
- Dropping partition with CASCADE drops constraints on partitioned table Vladyslav Hutych
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Thomas Munro
- Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12. Zaid Shabbir
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Thomas Munro
- Bug report for plpgsql Slivaev Dmitry
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan
- Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
- Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
- Re: Bug report for plpgsql David G. Johnston
- Re: Bug report for plpgsql Pavel Stehule