pgsql-bugs - July 2020

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 31

July 1, 2020

Thread Author Time
Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call' Reiner Peterke 07:25
Re: BUG #16519: SET SESSION ROLE in plpgsql requires string literal. Marianne B. Wiese 09:26
BUG #16522: No anti-violent cracking mechanism PG Bug reporting form 10:01
Re: BUG #16522: No anti-violent cracking mechanism Magnus Hagander 10:54
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table 📎 Dmitry Dolgov 12:55
Re: [bug] Table not have typarray when created by single user mode 📎 Tom Lane 16:47
Re: BUG #16521: n_distinct_inherited does not affect child partitions when set on main partition Klaudie Willis 17:16

July 2, 2020

Thread Author Time
BUG #16523: The wal logs fill the disk and are not cleaned up PG Bug reporting form 03:16
Re: BUG #15615: pg_upgrade and vacuum_defer_cleanup_age Laurenz Albe 09:33
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table Etsuro Fujita 11:52
Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 Tom Lane 16:51
Re: BUG #16521: n_distinct_inherited does not affect child partitions when set on main partition David Rowley 22:28

July 3, 2020

Thread Author Time
BUG #16524: PgAdmin for macbook users creates an overlay on the UI which disables all functionality of PgAdmin PG Bug reporting form 09:19
BUG #16525: Problème de connexion serveur PG Bug reporting form 14:20
BUG #16526: pg_test_fsync in v12 doesn't run in Windows PG Bug reporting form 16:01
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table Etsuro Fujita 17:35
Re: BUG #16525: Problème de connexion serveur Jehan-Guillaume de Rorthais 20:25

July 4, 2020

Thread Author Time
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Michael Paquier 01:03
BUG #16527: Valgrind detects an invalid read in brin_revmap_data with non-index page PG Bug reporting form 16:00
Re: BUG #16527: Valgrind detects an invalid read in brin_revmap_data with non-index page Tomas Vondra 20:04
Re: BUG #16527: Valgrind detects an invalid read in brin_revmap_data with non-index page Tomas Vondra 21:54

July 5, 2020

Thread Author Time
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table 📎 Etsuro Fujita 07:45
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table Dmitry Dolgov 16:58

July 6, 2020

Thread Author Time
BUG #16528: Analytical function with Over clause for ARRAY datatype is not working properly PG Bug reporting form 12:28
Re: BUG #16528: Analytical function with Over clause for ARRAY datatype is not working properly Tom Lane 13:48
Re: [bug] Table not have typarray when created by single user mode 📎 Tom Lane 20:22
Re: posgres 12 bug (partitioned table) 📎 Soumyadeep Chakraborty 22:45

July 7, 2020

Thread Author Time
Installation error 📎 Igor Federizi 01:33
TRUNCATE is made to wait when logical synchronous replication 📎 Keisuke Kuroda 01:59
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Michael Paquier 06:07
Re: Installation error Fahar Abbas 07:54
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows 📎 Michael Paquier 08:25
invalid alloc size error possible in shm_mq 📎 Markus Wanner 10:30
Re: posgres 12 bug (partitioned table) 📎 Amit Langote 14:18
Bug: Very poor query optimization by Postgres 📎 Tobias Völk 18:02
BUG #16529: Installation error/bug PG Bug reporting form 18:48
Re: Bug: Very poor query optimization by Postgres David G. Johnston 20:19

July 8, 2020

Thread Author Time
Re: posgres 12 bug (partitioned table) Soumyadeep Chakraborty 00:37
Re: posgres 12 bug (partitioned table) Amit Langote 02:16
Re: Bug: Very poor query optimization by Postgres Pavel Stehule 04:13
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table 📎 Etsuro Fujita 06:15
Re: Installation error Fahar Abbas 06:59
BUG #16530: pgAdmin 4 Query Tool not loading/visualizing the data PG Bug reporting form 09:07
Re: [bug] Table not have typarray when created by single user mode wenjing zeng 11:24
BUG #16531: listen_addresses wide open? PG Bug reporting form 13:20
RE: <EXTERNAL> Re: Invalid memory alloc querying field type bytea Thompson, Shon 15:25
Re: BUG #16531: listen_addresses wide open? Tom Lane 16:24
Re: posgres 12 bug (partitioned table) Soumyadeep Chakraborty 16:52
Re: BUG #16531: listen_addresses wide open? Tom Lane 21:57
Re: BUG #16531: listen_addresses wide open? Bee.Lists 22:03
Re: BUG #16531: listen_addresses wide open? David G. Johnston 22:21
Re: BUG #16531: listen_addresses wide open? Tom Lane 22:35
Re: BUG #16531: listen_addresses wide open? Bee.Lists 23:11
Re: BUG #16531: listen_addresses wide open? David G. Johnston 23:44

July 9, 2020

Thread Author Time
Re: BUG #16531: listen_addresses wide open? Bee.Lists 02:15
BUG #16532: Contact and "en_NZ.UTF-8" PG Bug reporting form 03:10
Re: posgres 12 bug (partitioned table) Amit Langote 07:16
Re: <EXTERNAL> Re: Invalid memory alloc querying field type bytea Joe Conway 14:23
Re: BUG #16529: Installation error/bug Devrim Gündüz 15:55
Re: fedora32 install guide error: "initdb" --> "--initdb" Devrim Gündüz 15:58
Re: BUG #16512: Character considered as a number by regex but can not convert to numeric tester357 17:07
Re: posgres 12 bug (partitioned table) Soumyadeep Chakraborty 17:56
Getting Error while using row_number() Ashish Kaushal 19:27
Re: Getting Error while using row_number() David G. Johnston 19:51
Re: Getting Error while using row_number() David G. Johnston 19:54
Re: Getting Error while using row_number() Tom Lane 20:09
Re: BUG #16512: Character considered as a number by regex but can not convert to numeric Tom Lane 20:29

July 10, 2020

Thread Author Time
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Michael Paquier 01:53
BUG #16533: Planner optimisation : range predicate not propagating to joined tables PG Bug reporting form 02:42
Re: posgres 12 bug (partitioned table) Amit Langote 06:23
TDE in PostgreSQL Євген Панченко 08:11
Re: posgres 12 bug (partitioned table) Amit Langote 11:43
Re: TDE in PostgreSQL Fabien COELHO 11:52
Re: TDE in PostgreSQL Hans-Jürgen Schönig (PostgreSQL) 12:26
BUG #16534: autovacuum_autoanalyze not working on latitude(earth) expression PG Bug reporting form 14:00
Re: BUG #16534: autovacuum_autoanalyze not working on latitude(earth) expression Tom Lane 14:36
Re: BUG #16534: autovacuum_autoanalyze not working on latitude(earth) expression Sergei Kornilov 19:58
BUG #16535: Implementing Autonomous Transactions in Postgresql PG Bug reporting form 21:30
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql Christophe Pettus 21:40
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql David G. Johnston 21:44

July 11, 2020

Thread Author Time
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql Konstantin Knizhnik 07:12
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql legrand legrand 08:01
postgresql 12 runs out of memory when updating a partitioned table with subquery Max Vikharev 20:32

July 12, 2020

Thread Author Time
Re: postgresql 12 runs out of memory when updating a partitioned table with subquery David Rowley 05:50
Re: BUG #16534: autovacuum_autoanalyze not working on latitude(earth) expression Martin Winkel 09:46
Re: postgresql 12 runs out of memory when updating a partitioned table with subquery Max Vikharev 12:06
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table 📎 Etsuro Fujita 12:55
Re: postgresql 12 runs out of memory when updating a partitioned table with subquery David Rowley 21:44

July 13, 2020

Thread Author Time
BUG #16536: Segfault with partition-wise joins PG Bug reporting form 12:59
Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting Arne Roland 13:14
Small query using LATERAL that segfaults Postgres Tom Ellis 17:51
Re: Small query using LATERAL that segfaults Postgres Pavel Stehule 18:27
BUG #16537: could not connect to database although database is running PG Bug reporting form 19:29
Re: BUG #16537: could not connect to database although database is running David G. Johnston 19:50
Re: BUG #16537: could not connect to database although database is running Tom Lane 20:01
Re: BUG #16536: Segfault with partition-wise joins Tom Lane 22:11
Re: BUG #16427: pgsql_tmp - temp files not released Murali Natti 22:44

July 14, 2020

Thread Author Time
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Bruce Momjian 00:06
Re: Small query using LATERAL that segfaults Postgres Tom Lane 00:40
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Michael Paquier 03:54
BUG #16539: About pg_logdir_ls() function and pg_ls_logdir()function PG Bug reporting form 04:29
Re: BUG #16539: About pg_logdir_ls() function and pg_ls_logdir()function David G. Johnston 06:06
BUG #16540: Possible corrupted file? PG Bug reporting form 08:10
Re: Small query using LATERAL that segfaults Postgres Tom Ellis 09:00
Re: Small query using LATERAL that segfaults Postgres David Rowley 09:04
ERROR: cache lookup failed for collation 0 on DELETE query after upgrading from 9.X to 12.3 cen 13:41
Re: ERROR: cache lookup failed for collation 0 on DELETE query after upgrading from 9.X to 12.3 cen 13:54
Re: BUG #16540: Possible corrupted file? Tom Lane 14:01
Re: ERROR: cache lookup failed for collation 0 on DELETE query after upgrading from 9.X to 12.3 Tom Lane 14:11
Re: BUG #16536: Segfault with partition-wise joins Andrew Gierth 14:24
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Bruce Momjian 14:27
Re: BUG #16540: Possible corrupted file? Paul Hatcher 14:53
Re: ERROR: cache lookup failed for collation 0 on DELETE query after upgrading from 9.X to 12.3 cen 15:42
Re: BUG #16536: Segfault with partition-wise joins 📎 Tom Lane 15:48
Re: ERROR: cache lookup failed for collation 0 on DELETE query after upgrading from 9.X to 12.3 📎 Tom Lane 16:29
BUG #16541: Timestamp allowing greater than max documented value? PG Bug reporting form 17:17
Re: BUG #16541: Timestamp allowing greater than max documented value? Tom Lane 17:59

July 15, 2020

Thread Author Time
BUG #16542: High CPU Usage PG Bug reporting form 03:17
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Michael Paquier 06:53
BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1 PG Bug reporting form 07:30
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table 📎 Etsuro Fujita 07:35
Re: BUG #16542: High CPU Usage David Rowley 07:35
Re: BUG #16501: Incorrect result. select multi_key_columns_range_partition_table Etsuro Fujita 07:48
Re: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1 Magnus Hagander 08:33
AW: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1 Marco Lechner 08:44
Re: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1 Magnus Hagander 08:48
Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table Dmitry Dolgov 10:03
AW: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1 Marco Lechner 10:34
Re: BUG #16542: High CPU Usage Arthur Nascimento 12:52
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Bruce Momjian 16:26
Re: BUG #16419: wrong parsing BC year in to_date() function 📎 David G. Johnston 16:26

July 16, 2020

Thread Author Time
BUG #16544: How to identify trigger is called from the node where row is created? PG Bug reporting form 04:54
Re: BUG #16544: How to identify trigger is called from the node where row is created? David G. Johnston 05:31
Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows Michael Paquier 07:19
BUG #16545: COALESCE evaluates arguments to the right of the first non-null argument PG Bug reporting form 13:09
Re: BUG #16545: COALESCE evaluates arguments to the right of the first non-null argument Tom Lane 14:14
Stored columns: Unexpected varattno in expression to be mapped Thiede, Christoph 15:43
Re: Stored columns: Unexpected varattno in expression to be mapped David G. Johnston 16:05
Re: Stored columns: Unexpected varattno in expression to be mapped Tom Lane 16:10

July 17, 2020

Thread Author Time
Re: Stored columns: Unexpected varattno in expression to be mapped Michael Paquier 00:50
AW: Stored columns: Unexpected varattno in expression to be mapped Thiede, Christoph 01:04
Reported type mismatch improperly 📎 Andy Fan 09:00
psql has some accessibility issues on Windows Jelte Fennema 10:39
Re: psql has some accessibility issues on Windows Pavel Stehule 10:55
Re: Reported type mismatch improperly David G. Johnston 16:23

July 18, 2020

Thread Author Time
Re: Reported type mismatch improperly Andy Fan 04:05
Re: Reported type mismatch improperly David G. Johnston 04:28
Buffers from parallel workers not accumulated to upper nodes with gather merge 📎 Jehan-Guillaume de Rorthais 14:02

July 19, 2020

Thread Author Time
Re: Reported type mismatch improperly 📎 Andy Fan 02:25
Improvement for query planner? (no, not about count(*) again ;-)) Tobias Völk 19:22
Re: psql has some accessibility issues on Windows Thomas Munro 23:32

July 20, 2020

Thread Author Time
Re: Buffers from parallel workers not accumulated to upper nodes with gather merge Amit Kapila 06:00
Re: Buffers from parallel workers not accumulated to upper nodes with gather merge Amit Kapila 07:01
Re: Buffers from parallel workers not accumulated to upper nodes with gather merge Jehan-Guillaume de Rorthais 07:59
Re: BUG #16460: Error when executing REFRESH MATERIALIZED VIEW WITH DATA; Sandeep Thakkar 09:18
Re: Buffers from parallel workers not accumulated to upper nodes with gather merge Amit Kapila 09:59
Re: Improvement for query planner? (no, not about count(*) again ;-)) Francisco Olarte 10:56
apt-get -yq purge postgresql-common shows interactive dialog Ruslan Mukhamedov 11:13
Re: Buffers from parallel workers not accumulated to upper nodes with gather merge Jehan-Guillaume de Rorthais 12:09
Re: Improvement for query planner? (no, not about count(*) again ;-)) Francisco Olarte 14:44
Re: Improvement for query planner? (no, not about count(*) again ;-)) Tom Lane 17:58
Re: Improvement for query planner? (no, not about count(*) again ;-)) Andres Freund 20:50

July 21, 2020

Thread Author Time
pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. tutiluren 06:30
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. Pavel Stehule 06:43
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. David G. Johnston 06:59
BUG #16547: ECPG can't CALL the procedure which has INOUT parameter PG Bug reporting form 07:44
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. Juan José Santamaría Flecha 09:12
Bug - 11.8 Panchal, Avanish 10:47
BUG #16548: Order by on array element giving disparity in result PG Bug reporting form 12:52
Re: BUG #16548: Order by on array element giving disparity in result Kieran McCusker 13:25
cannot find postgresqllogreaderadapter Charles Zeng 13:41
Re: BUG #16548: Order by on array element giving disparity in result Manvendra 13:51
BUG #16549: "CASE" not work properly , the function works properly on PostgreSQL 9.6.8 PG Bug reporting form 13:55
Re: BUG #16548: Order by on array element giving disparity in result Tom Lane 14:15
Re: Bug - 11.8 David G. Johnston 14:18
Re: BUG #16548: Order by on array element giving disparity in result Francisco Olarte 15:10
Re: Buffers from parallel workers not accumulated to upper nodes with gather merge 📎 Jehan-Guillaume de Rorthais 15:34
Re: BUG #16549: "CASE" not work properly , the function works properly on PostgreSQL 9.6.8 Pavel Stehule 15:35
BUG #16550: Problem with pg_service.conf PG Bug reporting form 16:20
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. David G. Johnston 17:53
Re: BUG #16550: Problem with pg_service.conf David G. Johnston 18:07
Re: BUG #16550: Problem with pg_service.conf Michał Lis 20:44

July 22, 2020

Thread Author Time
Re: cannot find postgresqllogreaderadapter Michael Paquier 01:50
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Michael Paquier 06:51
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. Juan José Santamaría Flecha 07:36
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Kyotaro Horiguchi 08:45
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Michael Paquier 09:37
BUG #16552: In Setup wizard, Locale "Spanish, Spain" present twice PG Bug reporting form 11:22
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Tom Lane 14:39
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. tutiluren 15:17
Re: BUG #16550: Problem with pg_service.conf Jeff Janes 15:29
Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. Juan José Santamaría Flecha 16:58
Re: BUG #16550: Problem with pg_service.conf Michał Lis 17:02
Re: BUG #16550: Problem with pg_service.conf Christophe Pettus 19:52
Re: BUG #16549: "CASE" not work properly , the function works properly on PostgreSQL 9.6.8 Pavel Stehule 21:18
Re: BUG #16550: Problem with pg_service.conf David G. Johnston 22:16
Re: BUG #16549: "CASE" not work properly , the function works properly on PostgreSQL 9.6.8 Tom Lane 22:17
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Tom Lane 22:38
Re: BUG #16550: Problem with pg_service.conf Jeff Janes 22:53
Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data Michael Paquier 23:16

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 31