Архив рассылок [pgsql-bugs]
Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
psql: FATAL: database “<text>” does not exist Naima Shaikh
RE: BUG #16031: Group by returns duplicate groups David Raymond
Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
RE: BUG #16031: Group by returns duplicate groups David Raymond
Re: psql: FATAL: database “<text>” does not exist David G. Johnston
Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
BUG #16032: pg_basebackup when running on Windows doesn't clean up on failure correctly PG Bug reporting form
RE: BUG #16031: Group by returns duplicate groups David Raymond
RE: BUG #16031: Group by returns duplicate groups David Raymond
Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
BUG #16033: segmentation fault when runing update PG Bug reporting form
Re: BUG #16033: segmentation fault when runing update Miha Vrhovnik
BUG #16034: `\set ECHO all` doesn't work for \e command PG Bug reporting form
RE: BUG #16031: Group by returns duplicate groups David Raymond
BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql PG Bug reporting form
Re: Write skew anmalies are found in SERIALIZABLE isolation Peter Geoghegan
BUG #16036: Segmentation fault while doing an update PG Bug reporting form
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
BUG #16037: Assertion fails in varbit_out PG Bug reporting form
Re: BUG #16037: Assertion fails in varbit_out Andres Freund
Re: Write skew anmalies are found in SERIALIZABLE isolation Konstantin Knizhnik
Re: BUG #16035: STATEMENT_TIMEOUT not working when we have singlequote usage inside CTE which is used in inner sql Tatsuo Ishii
Bugs in google search for Postgres database Satish Kumar
Re: Bugs in google search for Postgres database Jaime Soler
BUG #16038: Alter table - SegFault PG Bug reporting form
Re: [BUGS] bug or simply not enough stack space? Merlin Moncure
Re: BUG #16038: Alter table - SegFault Alvaro Herrera
Re: BUG #16038: Alter table - SegFault Andres Freund
BUG #16039: PANIC when activating replication slots in Postgres 12.0 64bit under Windows PG Bug reporting form
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan PG Bug reporting form
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16036: Segmentation fault while doing an update Peter Geoghegan
BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault PG Bug reporting form
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
AW: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Hans Buschmann
BUG #16042: incorrect .gitignore file PG Bug reporting form
Re: BUG #16036: Segmentation fault while doing an update Andres Freund
Re: BUG #16042: incorrect .gitignore file Andres Freund
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
Re: BUG #16035: STATEMENT_TIMEOUT not working when we have singlequote usage inside CTE which is used in inner sql Tatsuo Ishii
Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
Re: [PATCH] Re: BUG #16032: pg_basebackup when running on Windowsdoesn't clean up on failure correctly Michael Paquier
Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault Fahar Abbas
BUG #16043: Duplicate Entry Key Message on postgres PG Bug reporting form
RE: BUG #16031: Group by returns duplicate groups David Raymond
Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
Re: BUG #16031: Group by returns duplicate groups Tomas Vondra
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
BUG #16044: Could not send data to server PG Bug reporting form
RE: BUG #16031: Group by returns duplicate groups David Raymond
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
Re: BUG #16044: Could not send data to server David G. Johnston
BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 PG Bug reporting form
Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` settingshould be documented Bruce Momjian
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
BUG #16046: xpath returns CDATA tag along with the value in postgres 12 PG Bug reporting form
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
AW: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Hans Buschmann
Re: AW: install error Scott Laing
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Andres Freund
Re: BUG #16038: Alter table - SegFault Andres Freund
BUG #16047: please help my postgress page can't be uploaded perfectly PG Bug reporting form
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: please help, my postgress page can't be uploaded perfectly David G. Johnston
Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
BUG #16048: SQLSTATE 22P05 is not captured in exception clause PG Bug reporting form
BUG #16049: log_line_prefix=%a and log_connections - application_name missing PG Bug reporting form
BUG #16050: Server crash on CREATE TEXT SEARCH DICTIONARY with a wrong AffFile PG Bug reporting form
BUG #16051: PQgetvalue(res,0,0) is null, PQgetlength(res,0,0) is 10 PG Bug reporting form
BUG #16052: pg_dump --no-comments not working PG Bug reporting form
BUG #16053: Query planner performance regression in sql query with multiple CTE in v12 PG Bug reporting form
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
ERROR: invalid input syntax for integer: "0A000" McLaughlin, Michael
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
Re: ERROR: invalid input syntax for integer: "0A000" Tomas Vondra
BUG #16054: Slowest individual queries PG Bug reporting form
Re: BUG #16054: Slowest individual queries Tomas Vondra
BUG #16055: pgAdmin 4 - ERROR: operator does not exist: - oid PG Bug reporting form
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
BUG #16056: Actually PGADMIN4 PG Bug reporting form
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16056: Actually PGADMIN4 David G. Johnston
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16054: Slowest individual queries Jeff Janes
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Justin Pryzby
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
BUG #16057: Faulty PK violation PG Bug reporting form
BUG #16058: show session_user shows a not clear error message PG Bug reporting form
BUG #16059: Tab-completion of filenames in COPY commands removes required quotes PG Bug reporting form
Re: BUG #16059: Tab-completion of filenames in COPY commands removesrequired quotes Francisco Olarte
BUG #16060: JDBC - badly gets DateOffsetTime value from database PG Bug reporting form
Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
Re: Re: BUG #15929: logical decoding can not write down the analyse result when the output file is touched. movead.li@highgo.ca
Re: Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
BUG #16061: pgadmin PG Bug reporting form
Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database stan@marencik.cz
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
Re: BUG #16026: default_tablespace in postgresql.conf is used insteadof the database's default. Thomas Munro
BUG #16062: pg_restore using ssl certs PG Bug reporting form
BUG #16063: Error retrieving data from the server: INTERNAL SERVER ERROR: string indices must be integers PG Bug reporting form
Re: BUG #16062: pg_restore using ssl certs Ashutosh Sharma
RE: BUG #16026: default_tablespace in postgresql.conf is used insteadof the database's default. Crevon Virgile
Re: BUG #16063: Error retrieving data from the server: INTERNALSERVER ERROR: string indices must be integers David G. Johnston
BUG #16064: Ldap Authentication failing with pg_hba.conf entry PG Bug reporting form
postgres has no spinlock support on riscv rv64imafdc Robert Henry
Re: BUG #16064: Ldap Authentication failing with pg_hba.conf entry Yudhveer Kandukuri
Checking types for arguments Gavin M2301
Fwd: Checking types for arguments Gavin M2301
Re: BUG #16026: default_tablespace in postgresql.conf is usedinstead of the database's default. Alvaro Herrera
Re: BUG #16026: default_tablespace in postgresql.conf is usedinstead of the database's default. Alvaro Herrera
BUG #16065: The operation nodes in query plans outputted by EXPLAIN have no authoritative definitions. PG Bug reporting form
BUG #16066: Ldap Authentication failure on PostgreSQL 10.10 PG Bug reporting form
Re: postgres has no spinlock support on riscv rv64imafdc Andres Freund
BUG #16067: Failed system call was semget PG Bug reporting form
BUG #16068: Collate of 'Norwegian Bokmål' is problematic PG Bug reporting form
Re: BUG #16067: Failed system call was semget Tomas Vondra
BUG #16069: Error installing yum.rpm PG Bug reporting form
Re: BUG #16065: The operation nodes in query plans outputted byEXPLAIN have no authoritative definitions. Eric Toombs
BUG #16070: A double-free bug in interfaces/libpq/fe-secure-openssl.c PG Bug reporting form
Re: BUG #16035: STATEMENT_TIMEOUT not working when we have singlequote usage inside CTE which is used in inner sql Tatsuo Ishii
BUG #16071: Server crashes when 'numeric' data type is used on any plpython Function PG Bug reporting form
Incorrect rounding of double values at max precision Gilleain Torrance
Re: Incorrect rounding of double values at max precision Andrew Gierth
Re: Incorrect rounding of double values at max precision Andrew Gierth
Re: Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
RE: Incorrect rounding of double values at max precision Gilleain Torrance
RE: PGDG strech : postgresql-11-postgis-2.5 won't install beacause ofmissing dependency Bruno DUPUIS
Re: Incorrect rounding of double values at max precision Andrew Gierth
CSV file t psotgresql table m krishna
BUG #16072: Two transaction to delete all data, The result is not hopeful PG Bug reporting form
memory problems and crash of db when deleting data from table withthousands of partitions Josef Machytka
BUG #16073: pg_dump build crashes half way PG Bug reporting form
Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Tomas Vondra
Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Bruce Momjian
BUG #16074: Consistently link latest repo RPM release to pgdg-redhat-repo-latest PG Bug reporting form
BUG #16075: The favicon of https://www.postgresql.org is vague on MacBook Pro with retina display PG Bug reporting form
PostgreSQL 12 installation fails because locale name contained non-english characters Skjalg A. Skagen
BUG #16076: JIT causes huge delays in a complex query. jit=off solves it. PG Bug reporting form
BUG #16077: Sorting of table list depends on platform PG Bug reporting form
Re: BUG #16073: pg_dump build crashes half way Andres Freund
BUG #16078: Problems starting and running the app stack builder PG Bug reporting form
BUG #16079: Question Regarding the BUG #16064 PG Bug reporting form
Re: BUG #16067: Failed system call was semget Thomas Munro
BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. PG Bug reporting form
BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory. PG Bug reporting form
BUG #16082: TOAST's pglz_decompress access to uninitialized data, if the database is corrupted. PG Bug reporting form
Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
BUG #16083: Different Result PG Bug reporting form
Re: BUG #16083: Different Result Pavel Stehule
RE: BUG #15858: could not stat file - over 4GB william allen
RE: BUG #15858: could not stat file - over 4GB william allen
Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Josef Machytka
Re: BUG #16079: Question Regarding the BUG #16064 Stephen Frost
Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Tomas Vondra
Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha
Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha
BUG #16084: Server couldn't be contacted PG Bug reporting form
BUG #16085: Potential missing version information available for /usr/pgsql-12/lib/libpq.so.5 PG Bug reporting form
Backup/restore problem Pavel Popov
BUG #16086: Cannot connect using psql, however I can connect using pgadmin PG Bug reporting form
Re: BUG #16084: Server couldn't be contacted Ashutosh Sharma
Re: Backup/restore problem Tom Lane
BUG #16087: Segmentation fault on ALTER TABLE PG Bug reporting form
BUG #16088: Multiple foreigh keys created on "ALTER TABLE" command PG Bug reporting form
Re: Backup/restore problem Pavel Popov
insert into inet from text automatically adding subnet Jeremy Finzel
BUG #16089: Index only scan does not happen but expected PG Bug reporting form
RE: BUG #16089: Index only scan does not happen but expected Stepan Yankevych
Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Josef Machytka
BUG #16090: Migración con pg_dump PG Bug reporting form
RE: BUG #16089: Index only scan does not happen but expected Stepan Yankevych
BUG #16091: xpath fails to compute "name()", regression PG Bug reporting form
Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Tomas Vondra
Re: BUG #16082: TOAST's pglz_decompress access to uninitializeddata, if the database is corrupted. Alvaro Herrera
Re: BUG #16090: Migración conpg_dump Alvaro Herrera
