pgsql-bugs - April 2019

If you find a bug, please use the bug reporting form.

Search the Archives

(enter a message-id to go directly to that message)
Advanced Search

Browse Archives

Prev | Next
Jump to day: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

April 1, 2019

Thread Author Time
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita 05:35
Re: BUG #15724: Can't create foreign table as partition 📎 Etsuro Fujita 06:01
Re: BUG #15724: Can't create foreign table as partition Amit Langote 06:23
BUG #15725: pgAgent not working on Another database other than Postgres PG Bug reporting form 06:32
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita 06:40
Re: BUG #15724: Can't create foreign table as partition Amit Langote 06:45
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita 06:57
BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker PG Bug reporting form 11:12
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Michael Paquier 13:29
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker ANASTACIO Tiago 13:49
Parallel query execution introduces performance regressions Jinho Jung 18:30
Re: Parallel query execution introduces performance regressions Andres Freund 18:34
Re: Parallel query execution introduces performance regressions Peter Geoghegan 18:52
Re: Parallel query execution introduces performance regressions Andres Freund 19:00
Re: Parallel query execution introduces performance regressions Peter Geoghegan 19:05
Re: Parallel query execution introduces performance regressions Jinho Jung 19:08
Re: Parallel query execution introduces performance regressions Andres Freund 19:13
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Thomas Munro 21:59

April 2, 2019

Thread Author Time
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Thomas Munro 00:24
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Thomas Munro 00:32
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Peter Geoghegan 00:41
Re: Parallel query execution introduces performance regressions David Rowley 03:21
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker ANASTACIO Tiago 09:59
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Thomas Munro 10:23
BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed PG Bug reporting form 10:30
BUG #15728: an index that created with keyword ONLY, when add new partition ,should not be auto created PG Bug reporting form 10:36
Re: BUG #15728: an index that created with keyword ONLY, when add new partition ,should not be auto created David G. Johnston 15:12
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane 15:19
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 15:29
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane 15:44
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 15:47
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Alvaro Herrera 15:51
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane 15:51
BUG #15729: Error 'invalid memory alloc request size' during updating a big xml field PG Bug reporting form 15:53
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 16:00
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 16:13
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Alvaro Herrera 17:00
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 17:04
Re: BUG #15722: 9000x performance regression on query starting PostgreSQL 10 due to bad query plan Jeff Janes 17:10
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 17:11
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane 17:13
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 17:17
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Alvaro Herrera 17:17
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane 17:30
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Жарков Роман 17:35
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 17:35
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker 📎 Thomas Munro 19:54

April 3, 2019

Thread Author Time
BUG #15730: Using filter function to interpolate data, the length limit of table field is invalid PG Bug reporting form 03:58
BUG #15731: CVE-2019-9193 PG Bug reporting form 07:38
Re: BUG #15731: CVE-2019-9193 Magnus Hagander 07:42
RE: Re: BUG #15731: CVE-2019-9193 Rajwade, Abhijit 07:46
Re: Re: BUG #15731: CVE-2019-9193 Magnus Hagander 08:10
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 08:29
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 r.zharkov 08:38
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Alvaro Herrera 12:20
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 12:59
Bug report - incorrect value displayed in jsonb column for large numbers Michał Iwańczuk 13:29
BUG #15732: Jessie backports removed from network PG Bug reporting form 15:29
Re: Bug report - incorrect value displayed in jsonb column for large numbers Tom Lane 16:48
Re: BUG #15383: Join Filter cost estimation problem in 10.5 Tom Lane 17:07
Re: Bug report - incorrect value displayed in jsonb column for large numbers Jerry Sievert 17:30
BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails PG Bug reporting form 18:22

April 4, 2019

Thread Author Time
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails Michael Paquier 01:35
Re: BUG #15383: Join Filter cost estimation problem in 10.5 David Rowley 04:37
Re: BUG #15722: 9000x performance regression on query starting PostgreSQL 10 due to bad query plan Jeremy Evans 06:16
BUG #15734: Walsender process crashing when executing SHOW ALL; PG Bug reporting form 07:54
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails 📎 Amit Langote 10:31
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails Michael Paquier 10:48
BUG #15735: postgis extension missing PG Bug reporting form 12:59
Bug trying to view table Rossiter, Russell D. 14:36
BUG #15736: running bootstrap script ... FATAL: invalid value for parameter "port": "" PG Bug reporting form 15:08
Re: BUG #15735: postgis extension missing bricklen 17:28
Re: Bug trying to view table bricklen 17:42
Re: BUG #15735: postgis extension missing Prakash Ramakrishnan 17:52
Re: BUG #15735: postgis extension missing Tom Lane 19:35
Re: BUG #15735: postgis extension missing Prakash Ramakrishnan 19:40
BUG #15737: Unexpectedly Deleting full table when referring CTE (With Clause ) data,in a Subquery in another CTE PG Bug reporting form 20:08
Re: BUG #15737: Unexpectedly Deleting full table when referring CTE (With Clause ) data,in a Subquery in another CTE David G. Johnston 20:26

April 5, 2019

Thread Author Time
Re: BUG #15737: Unexpectedly Deleting full table when referring CTE (With Clause ) data,in a Subquery in another CTE David Rowley 00:43
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails 📎 Amit Langote 03:22
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails 📎 Amit Langote 05:07
BUG #15738: _SPI_connected fail PG Bug reporting form 06:40
Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita 12:07

April 6, 2019

Thread Author Time
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 Tom Lane 16:23
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 16:28
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 17:09
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 Andres Freund 17:10
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 17:17
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 17:27
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 23:10

April 7, 2019

Thread Author Time
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 Andres Freund 20:33

April 8, 2019

Thread Author Time
BUG #15739: PgAdmin4 4.4 does not work with latest psycopg2 (2.8.1) PG Bug reporting form 02:59
Re: BUG #15739: PgAdmin4 4.4 does not work with latest psycopg2 (2.8.1) Rizwan Wangde 03:02
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails Michael Paquier 04:50
Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails Amit Langote 04:55
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 Amit Langote 07:21
Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Michael Paquier 07:39
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 Amit Langote 08:18
PostgreSQL 9.5 service stopped intermittently on windows 10 Pro version 1703. Kadam, Daulat (BHGE, consultant) 10:23
BUG #15740: Problem with the creation of prodecures, synonyms and packages PG Bug reporting form 12:49
BUG #15741: ERROR: failed to build any 3-way joins PG Bug reporting form 13:32
Re: BUG #15740: Problem with the creation of prodecures, synonyms and packages Pavel Stehule 13:41
Re: BUG #15740: Problem with the creation of prodecures, synonyms and packages André Free 13:56
Re: BUG #15740: Problem with the creation of prodecures, synonyms and packages Pavel Stehule 13:57
Re: BUG #15741: ERROR: failed to build any 3-way joins Tom Lane 14:13
Re: PostgreSQL 9.5 service stopped intermittently on windows 10 Pro version 1703. Julien Rouhaud 14:20
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane 16:31
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Andres Freund 16:41
Re: BUG #15741: ERROR: failed to build any 3-way joins Tom Lane 20:13

April 9, 2019

Thread Author Time
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Amit Langote 04:55
BUG #15742: Postgres Service is not starting after Windows abrupt Shutdown PG Bug reporting form 05:32
Re: BUG #15742: Postgres Service is not starting after Windows abrupt Shutdown Michael Paquier 06:54
Re: BUG #15741: ERROR: failed to build any 3-way joins SKORSKI Anthony 08:00
RE: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows 10 Pro version 1703. 📎 Kadam, Daulat (BHGE, consultant) 09:26
Re: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows 10 Pro version 1703. Julien Rouhaud 10:06
BUG #15743: pg_tblspc Sharing violation with MSSQL, therefore PostgreSQL is running into Timeout at startup PG Bug reporting form 13:59
Re: BUG #15698: to_char doesn't return expected value with negative INTERVAL Bruce Momjian 17:23
Re: BUG #15698: to_char doesn't return expected value with negative INTERVAL s.celles@gmail.com 18:21
BUG #15744: Replication slot peak query throwing error for wrong sequence entry for toast chunk PG Bug reporting form 20:09
BUG #15745: WAL References Invalid Pages...that eventually resolves PG Bug reporting form 20:29
Unexpected behaviour, definitely looks like a bug. Leshchuk Aleksey 21:38
Re: Unexpected behaviour, definitely looks like a bug. Nikolay Samokhvalov 22:03
Re: Unexpected behaviour, definitely looks like a bug. David G. Johnston 23:02

April 10, 2019

Thread Author Time
Failure of initdb Bruce Rindahl 01:17
BUG #15746: cache lookup failed for function in plpgsql block PG Bug reporting form 03:51
Re: BUG #15734: Walsender process crashing when executing SHOW ALL; 📎 Michael Paquier 06:04
Re: BUG #15744: Replication slot peak query throwing error for wrong sequence entry for toast chunk Peter Eisentraut 08:28
Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Alvaro Herrera 15:01
Re: BUG #15744: Replication slot peak query throwing error for wrong sequence entry for toast chunk Andres Freund 15:45
Re: BUG #15737: Unexpectedly Deleting full table when referring CTE (With Clause ) data,in a Subquery in another CTE Chandan Ahuja 20:59
Suspicious strcmp() in src/backend/parser/parse_expr.c Rikard Falkeborn 21:40
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Andrew Gierth 22:33
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Tom Lane 22:43

April 11, 2019

Thread Author Time
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier 02:19
Re: BUG #15734: Walsender process crashing when executing SHOW ALL; 📎 Michael Paquier 03:07
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Thomas Munro 03:26
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 03:29
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c David Rowley 03:43
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier 03:46
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Michael Paquier 03:47
Re: BUG #15709: if drop exists syntax Jueve L 03:53
Re: BUG #15709: if drop exists syntax Pavel Stehule 04:00
Re: BUG #15709: if drop exists syntax Jueve L 04:17
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Жарков Роман 04:17
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Michael Paquier 04:23
Re: BUG #15709: if drop exists syntax Pavel Stehule 04:32
Re: BUG #15709: if drop exists syntax Jueve L 04:43
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Thomas Munro 04:44
Re: BUG #15709: if drop exists syntax Pavel Stehule 04:47
Re: BUG #15709: if drop exists syntax Jueve L 04:51
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Tom Lane 04:55
Re: BUG #15709: if drop exists syntax Pavel Stehule 05:00
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 05:35
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c 📎 Michael Paquier 06:50
Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Michael Paquier 06:57
Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Amit Langote 06:58
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed 📎 Thomas Munro 08:52
BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 PG Bug reporting form 08:53
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 08:55
Re: BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 Sergei Kornilov 08:58
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Daniel Gustafsson 08:59
Re: BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 Tobias Gierke 09:05
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker 📎 Thomas Munro 10:51
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Daniel Gustafsson 11:39
Re: BUG #15746: cache lookup failed for function in plpgsql block 📎 Kyotaro HORIGUCHI 12:11
BUG #15748: arrow keys doesn't work PG Bug reporting form 12:50
List of issues with 4.5 that need to be fixed Rossiter, Russell D. 13:20
Re: BUG #15748: arrow keys doesn't work Christoph Berg 13:58
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c David Rowley 14:06
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Tom Lane 14:12
Re: List of issues with 4.5 that need to be fixed Christopher Browne 15:01
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane 15:04
Re: List of issues with 4.5 that need to be fixed Alvaro Herrera 15:06

April 12, 2019

Thread Author Time
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier 00:58
Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier 01:29
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed r.zharkov 02:44
Re: BUG #15746: cache lookup failed for function in plpgsql block r.zharkov 03:22
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Michael Paquier 03:32
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Thomas Munro 05:04
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Michael Paquier 05:19
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Thomas Munro 05:39
BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned PG Bug reporting form 13:38
On replicas, checkpoints_req is incremented even if restartpoint has not happened Nikolay Samokhvalov 13:43
Re: BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned Sergei Kornilov 13:44
Re: BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query Sergei Kornilov 13:48
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane 16:47
Re: BUG #15746: cache lookup failed for function in plpgsql block Tom Lane 16:55

April 13, 2019

Thread Author Time
Re: Error occurred when i install in my pc. vinodh kumar gulumuru 15:06
Re: Error occurred when i install in my pc. vinodh kumar gulumuru 15:27
BUG #15750: don't have server PG Bug reporting form 17:08
BUG #15751: Unexpected behaviour at plainto_tsquery funciton PG Bug reporting form 21:11
Re: BUG #15751: Unexpected behaviour at plainto_tsquery funciton Daniel Gustafsson 21:27

April 14, 2019

Thread Author Time
Re: Error occurred when i install in my pc. Sandeep Thakkar 10:08
BUG #15752: Declarative partitions trigger with function attributes - empty attributes list on each partition PG Bug reporting form 11:51
BUG #15753: FullText search cannot find bird, rat from birds, rats PG Bug reporting form 16:29
Re: BUG #15753: FullText search cannot find bird, rat from birds, rats Jeff Janes 17:29
BUG #15754: The CentOS RPM for PostgreSQL 11 disappeared and now throws a 404 error PG Bug reporting form 19:36

April 15, 2019

Thread Author Time
Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Michael Paquier 03:39
Re: Error occurred when i install in my pc. Sandeep Thakkar 03:49
Re: Error occurred when i install in my pc. vinodh kumar gulumuru 04:30

Browse Archives

Prev | Next
Jump to day: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30