Архив рассылок [pgsql-bugs]
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
BUG #15725: pgAgent not working on Another database other than Postgres PG Bug reporting form
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker PG Bug reporting form
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Michael Paquier
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker ANASTACIO Tiago
Re: Parallel query execution introduces performance regressions Peter Geoghegan
Re: Parallel query execution introduces performance regressions Peter Geoghegan
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Peter Geoghegan
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker ANASTACIO Tiago
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed PG Bug reporting form
BUG #15728: an index that created with keyword ONLY, when add new partition ,should not be auto created PG Bug reporting form
Re: BUG #15728: an index that created with keyword ONLY, when add newpartition ,should not be auto created David G. Johnston
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane
BUG #15729: Error 'invalid memory alloc request size' during updating a big xml field PG Bug reporting form
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
BUG #15730: Using filter function to interpolate data, the length limit of table field is invalid PG Bug reporting form
BUG #15731: CVE-2019-9193 PG Bug reporting form
Re: BUG #15731: CVE-2019-9193 Magnus Hagander
RE: Re: BUG #15731: CVE-2019-9193 Rajwade, Abhijit
Re: Re: BUG #15731: CVE-2019-9193 Magnus Hagander
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
BUG #15732: Jessie backports removed from network PG Bug reporting form
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Michael Paquier
Re: BUG #15722: 9000x performance regression on query startingPostgreSQL 10 due to bad query plan Jeremy Evans
BUG #15734: Walsender process crashing when executing SHOW ALL; PG Bug reporting form
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Michael Paquier
BUG #15735: postgis extension missing PG Bug reporting form
Bug trying to view table Rossiter, Russell D.
BUG #15736: running bootstrap script ... FATAL: invalid value for parameter "port": "" PG Bug reporting form
Re: Bug trying to view table bricklen
Re: BUG #15735: postgis extension missing Prakash Ramakrishnan
Re: BUG #15735: postgis extension missing Prakash Ramakrishnan
Re: BUG #15737: Unexpectedly Deleting full table when referring CTE(With Clause ) data,in a Subquery in another CTE David Rowley
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
BUG #15738: _SPI_connected fail PG Bug reporting form
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
BUG #15739: PgAdmin4 4.4 does not work with latest psycopg2 (2.8.1) PG Bug reporting form
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Michael Paquier
Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
PostgreSQL 9.5 service stopped intermittently on windows 10 Proversion 1703. Kadam, Daulat (BHGE, consultant)
BUG #15740: Problem with the creation of prodecures, synonyms and packages PG Bug reporting form
BUG #15741: ERROR: failed to build any 3-way joins PG Bug reporting form
BUG #15742: Postgres Service is not starting after Windows abrupt Shutdown PG Bug reporting form
Re: BUG #15741: ERROR: failed to build any 3-way joins SKORSKI Anthony
RE: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows10 Pro version 1703. Kadam, Daulat (BHGE, consultant)
Re: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows10 Pro version 1703. Julien Rouhaud
BUG #15743: pg_tblspc Sharing violation with MSSQL, therefore PostgreSQL is running into Timeout at startup PG Bug reporting form
Re: BUG #15698: to_char doesn't return expected value with negative INTERVAL s.celles@gmail.com
BUG #15744: Replication slot peak query throwing error for wrong sequence entry for toast chunk PG Bug reporting form
BUG #15745: WAL References Invalid Pages...that eventually resolves PG Bug reporting form
Unexpected behaviour, definitely looks like a bug. Leshchuk Aleksey
Re: Unexpected behaviour, definitely looks like a bug. Nikolay Samokhvalov
Re: Unexpected behaviour, definitely looks like a bug. David G. Johnston
Failure of initdb Bruce Rindahl
BUG #15746: cache lookup failed for function in plpgsql block PG Bug reporting form
Re: BUG #15744: Replication slot peak query throwing error for wrongsequence entry for toast chunk Peter Eisentraut
Re: BUG #15744: Replication slot peak query throwing error for wrongsequence entry for toast chunk Andres Freund
Re: BUG #15737: Unexpectedly Deleting full table when referring CTE(With Clause ) data,in a Subquery in another CTE Chandan Ahuja
Suspicious strcmp() in src/backend/parser/parse_expr.c Rikard Falkeborn
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
Re: BUG #15709: if drop exists syntax Pavel Stehule
Re: BUG #15709: if drop exists syntax Pavel Stehule
Re: BUG #15709: if drop exists syntax Pavel Stehule
Re: BUG #15709: if drop exists syntax Pavel Stehule
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 PG Bug reporting form
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
Re: BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 Sergei Kornilov
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Daniel Gustafsson
Re: BUG #15747: Help says 'application_name' property supports 64characters in a standard built but it's only 63 Tobias Gierke
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Daniel Gustafsson
Re: BUG #15746: cache lookup failed for function in plpgsql block Kyotaro HORIGUCHI
BUG #15748: arrow keys doesn't work PG Bug reporting form
List of issues with 4.5 that need to be fixed Rossiter, Russell D.
Re: BUG #15748: arrow keys doesn't work Christoph Berg
Re: List of issues with 4.5 that need to be fixed Christopher Browne
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane
Re: List of issues with 4.5 that need to be fixed Alvaro Herrera
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
Re: BUG #15746: cache lookup failed for function in plpgsql block r.zharkov@postgrespro.ru
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Michael Paquier
BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned PG Bug reporting form
On replicas, checkpoints_req is incremented even if restartpoint hasnot happened Nikolay Samokhvalov
Re: BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned Sergei Kornilov
Re: Error occurred when i install in my pc. vinodh kumar gulumuru
Re: Error occurred when i install in my pc. vinodh kumar gulumuru
BUG #15750: don't have server PG Bug reporting form
BUG #15751: Unexpected behaviour at plainto_tsquery funciton PG Bug reporting form
Re: BUG #15751: Unexpected behaviour at plainto_tsquery funciton Daniel Gustafsson
Re: Error occurred when i install in my pc. Sandeep Thakkar
BUG #15752: Declarative partitions trigger with function attributes - empty attributes list on each partition PG Bug reporting form
BUG #15753: FullText search cannot find bird, rat from birds, rats PG Bug reporting form
BUG #15754: The CentOS RPM for PostgreSQL 11 disappeared and now throws a 404 error PG Bug reporting form
Re: Error occurred when i install in my pc. Sandeep Thakkar
Re: Error occurred when i install in my pc. vinodh kumar gulumuru
BUG #15755: After upgrading to 9.6.12 using pg_upgrade, select query does not return the expected results. PG Bug reporting form
BUG #15756: Seemingly inconsistent behavior of SUBSTRING(string FROM pattern FOR escape) function PG Bug reporting form
Re: BUG #15756: Seemingly inconsistent behavior of SUBSTRING(stringFROM pattern FOR escape) function Daniel Gustafsson
Re: BUG #15756: Seemingly inconsistent behavior of SUBSTRING(stringFROM pattern FOR escape) function Francisco Olarte
RE: [EXTERNAL] Re: List of issues with 4.5 that need to be fixed Rossiter, Russell D.
BUG #15757: Problem with the sequences node PG Bug reporting form
Re: BUG #15757: Problem with the sequences node David G. Johnston
Re: Error occurred when i install in my pc. vinodh kumar gulumuru
Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Suresh Thelkar
Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. David G. Johnston
BUG #15758: regr_* return wrong answers for some valid data PG Bug reporting form
Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Suresh Thelkar
BUG #15759: Lot of idle connection created by "SET extra_float_digits = 3" PG Bug reporting form
BUG #15760: Error to start PGAdmin 4.5 PG Bug reporting form
BUG #15761: ODBC: SQLForeignKeys-ResultSet-Column 'deferrablity' PG Bug reporting form
BUG #15762: Download URL not found PG Bug reporting form
BUG #15763: JSON nulls not handled properly PG Bug reporting form
Re: BUG #15763: JSON nulls not handled properly David G. Johnston
Re: BUG #15763: JSON nulls not handled properly Jacob Crell
BUG #15764: Yum repo/key name mismatch PG Bug reporting form
Re: Error occurred when i install in my pc. Sandeep Thakkar
Fw: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causesthe standby to fail to start stream replication soumitra bhandary
Re: BUG #15764: Yum repo/key name mismatch Devrim Gündüz
BUG #15765: pgdg-redhat-repo-42.0-3 gpgkey entries don't exist in /etc/yum.repos.d/pgdg-redhat-all.repo PG Bug reporting form
Re: Fw: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causes the standby to fail to start stream replication Devrim Gündüz
BUG #15766: discard plans bug. database CRASH PG Bug reporting form
BUG #15767: Export fails 'worker process died unexpectedly' but no error in pg_dump PG Bug reporting form
BUG #15768: Removed rpms and now require /etc/redhat-release PG Bug reporting form
Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Suresh Thelkar
BUG #15769: The database cluster intialisation failed. PG Bug reporting form
Re: Error occurred when i install in my pc. vinodh kumar gulumuru
pgAdmin bug? Fabrizio Mazzoni
BUG #15770: PostgreSQL rpm package got to be impossible to be installed in Amazon Linux 2 PG Bug reporting form
Re: Requiring temp tables to have replication identity defined Peter Eisentraut
BUG #15771: PgAdmin 4.5 don't listing sequences. PG Bug reporting form
Installing latest psqlodbc rel 11.00.0000-x64 on windows server Maurizio Bellon
BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 PG Bug reporting form
Re: BUG #15772: Some messages in log files are in ANSI encodingwhile server encoding is UTF8 Bruce Momjian
Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 Eugene Podshivalov
Re: BUG #15772: Some messages in log files are in ANSI encodingwhile server encoding is UTF8 Bruce Momjian
Re: BUG #15772: Some messages in log files are in ANSI encodingwhile server encoding is UTF8 Alvaro Herrera
Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 Tom Lane
Re: Re: BUG #15769: The database cluster intialisation failed. Sandeep Thakkar
BUG #15773: Cannot Open a sql file directly - have to go to pgadmin, query tool and then choose open PG Bug reporting form
Re: xpath insert unexpected newlines Tom Lane
BUG #15774: Postgresql installation error with BIGSql PG Bug reporting form
amcheck assert failure Grigory Smolkin
Re: amcheck assert failure Peter Geoghegan
Re: amcheck assert failure Grigory Smolkin
Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: amcheck assert failure Peter Geoghegan
Re: amcheck assert failure Peter Geoghegan
Re: amcheck assert failure Peter Geoghegan
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Stephen Frost
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: amcheck assert failure Grigory Smolkin
Re: amcheck assert failure Peter Geoghegan
Re: amcheck assert failure Grigory Smolkin
Re: xpath insert unexpected newlines Tom Lane
Re: amcheck assert failure Peter Geoghegan
Re: amcheck assert failure Tom Lane
Re: amcheck assert failure Peter Geoghegan
Re: amcheck assert failure Tom Lane
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: amcheck assert failure Peter Geoghegan
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
BUG #15775: pg_get_indexdef: could not open relation with OID 16385 PG Bug reporting form
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
Re: Possible to store invalid SCRAM-SHA-256 Passwords Stephen Frost
Re: Possible to store invalid SCRAM-SHA-256 Passwords Stephen Frost
BUG #15776: Pgpool PG Bug reporting form
Re: BUG #15776: Pgpool Jonathan S. Katz
Re: BUG #15776: Pgpool Tatsuo Ishii
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
Re: amcheck assert failure Grigory Smolkin
bug: evil autoConcat when each string is on new line Jan Skydánek
Re: bug: evil autoConcat when each string is on new line Alvaro Herrera
BUG #15777: Unexpected error in select from view with set-returning function and union PG Bug reporting form
Re: BUG #15777: Unexpected error in select from view with set-returning function and union Sergei Kornilov
CREATE SUBSCRIPTION fails with long passwords Mike Lissner
Re: amcheck assert failure Peter Geoghegan
BUG #15778: Replication slot peak query cause memory spike at the server when big transaction are running PG Bug reporting form
Re: amcheck assert failure Peter Geoghegan
Re: CREATE SUBSCRIPTION fails with long passwords Tomas Vondra
Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs Michael Paquier
Re: CREATE SUBSCRIPTION fails with long passwords Paul Mansueto Namuag
Re: bug: evil autoConcat when each string is on new line Francisco Olarte
Re: bug: evil autoConcat when each string is on new line Pavel Stehule
BUG #15779: Partition elimination doesn't work as expected when using PARTITION BY RANGE PG Bug reporting form
BUG #15780: Win10 PGS11 installer includes psAdmin3 LTS which does not support PGS11 PG Bug reporting form
BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) PG Bug reporting form
Re: bug: evil autoConcat when each string is on new line Francisco Olarte
BUG #15782: Error in pgAdmin4.5 PG Bug reporting form
Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Amit Langote
Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Damir Ciganović-Janković
Reg: Postgresql8.3 Using on Ubuntu neelaveni
Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
Re: BUG #15631: Generated as identity field in a temporary table withon commit drop corrupts system catalogs Peter Eisentraut
Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs Michael Paquier
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
Re: Reg: Postgresql8.3 Using on Ubuntu Andrew Gierth
BUG #15783: Fail to select with a function in FROM clause plus another table PG Bug reporting form
BUG #15784: logical replication replicate data of type array for operation insert but update/delete/truncate PG Bug reporting form
Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Amit Langote
Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Damir Ciganović-Janković
Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
Re: BUG #15631: Generated as identity field in a temporary table withon commit drop corrupts system catalogs Peter Eisentraut
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
BUG #15785: create slave through archive log replication PG Bug reporting form
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
BUG #15786: Matching version issue between postgres.exe and initdb.exe PG Bug reporting form
BUG #15787: Statement logging may consume huge amounts of memory when BYTEA parameters are involved. PG Bug reporting form
Current HEAD creates dumps that can't be loaded hubert depesz lubaczewski
