pgsql-hackers since 2020-06-24 00:00

The PostgreSQL developers team lives here. Discussion of current development issues, problems and bugs, and proposed new features. If your question cannot be answered by people in the other lists, and it is likely that only a developer will know the answer, you may re-post your question in this list. You must try elsewhere first!

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

June 24, 2020

Thread Author Time
Re: Assertion failure in pg_copy_logical_replication_slot() Alvaro Herrera 00:38
Re: Threading in BGWorkers (!) Andres Freund 01:44
Re: Threading in BGWorkers (!) Chapman Flack 01:50
Re: Threading in BGWorkers (!) Andres Freund 02:06
Re: Removal of currtid()/currtid2() and some table AM cleanup Michael Paquier 02:11
Re: Default setting for enable_hashagg_disk David Rowley 02:11
Re: Threading in BGWorkers (!) Tom Lane 02:13
Re: Review for GetWALAvailability() 📎 Kyotaro Horiguchi 02:15
Re: EXPLAIN: Non-parallel ancestor plan nodes exclude parallel worker instrumentation Amit Kapila 02:55
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Kyotaro Horiguchi 02:56
Re: Threading in BGWorkers (!) Chapman Flack 02:57
Re: Threading in BGWorkers (!) Tom Lane 03:08
Re: Default setting for enable_hashagg_disk Justin Pryzby 03:14
Re: Threading in BGWorkers (!) Chapman Flack 03:30
Re: Parallel Seq Scan vs kernel read ahead 📎 David Rowley 03:52
Re: Update InsertPgAttributeTuple comment to match new signature Michael Paquier 06:16
Allow CURRENT_ROLE in GRANTED BY 📎 Peter Eisentraut 06:35
should libpq also require TLSv1.2 by default? Peter Eisentraut 06:39
Re: EXPLAIN: Non-parallel ancestor plan nodes exclude parallel worker instrumentation Maciek Sakrejda 07:11
RE: [PoC] Non-volatile WAL buffer 📎 Takashi Menjo 07:43
Re: Improve handling of parameter differences in physical replication 📎 Peter Eisentraut 08:00
Re: Parallel copy 📎 Bharath Rupireddy 08:10
Re: Allow CURRENT_ROLE in GRANTED BY Vik Fearing 08:12
Re: Removal of currtid()/currtid2() and some table AM cleanup Inoue, Hiroshi 08:20
Re: [Patch] ALTER SYSTEM READ ONLY tushar 08:24
Re: should libpq also require TLSv1.2 by default? 📎 Daniel Gustafsson 08:33
Re: should libpq also require TLSv1.2 by default? Magnus Hagander 08:46
Re: Parallel copy Bharath Rupireddy 08:46
Re: pg_resetwal --next-transaction-id may cause database failed to restart. [email protected] 08:49
Re: Removal of currtid()/currtid2() and some table AM cleanup Michael Paquier 09:00
Re: should libpq also require TLSv1.2 by default? Daniel Gustafsson 09:01
PostgreSQL and big data - FDW ROS Didier 09:05
Re: Default setting for enable_hashagg_disk Bruce Momjian 09:06
Re: EXPLAIN: Non-parallel ancestor plan nodes exclude parallel worker instrumentation Amit Kapila 09:07
Re: min_safe_lsn column in pg_replication_slots view Fujii Masao 09:07
Re: min_safe_lsn column in pg_replication_slots view Fujii Masao 09:09
Re: PostgreSQL and big data - FDW Bruce Momjian 09:13
Re: Assertion failure in pg_copy_logical_replication_slot() 📎 Fujii Masao 09:16
Re: EXPLAIN: Non-parallel ancestor plan nodes exclude parallel worker instrumentation Amit Kapila 09:44
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Fujii Masao 09:45
[PATCH] COPY command's data format option allows only lowercase csv, text or binary 📎 Bharath Rupireddy 09:50
Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions Amit Kapila 10:34
Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions Amit Kapila 10:40
Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions Dilip Kumar 10:57
Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions Amit Kapila 11:08
Re: [HACKERS] Custom compression methods Robert Haas 11:59
Why forbid "INSERT INTO t () VALUES ();" Fabien COELHO 12:18
Re: Why forbid "INSERT INTO t () VALUES ();" Thomas Kellerer 12:23
Re: Default setting for enable_hashagg_disk David Rowley 12:24
Re: Default setting for enable_hashagg_disk Justin Pryzby 12:38
RE: PostgreSQL and big data - FDW ROS Didier 12:39
Re: min_safe_lsn column in pg_replication_slots view Amit Kapila 12:49
Re: [PATCH] COPY command's data format option allows only lowercase csv, text or binary Tom Lane 14:27
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Alvaro Herrera 14:58
Re: Assertion failure in pg_copy_logical_replication_slot() Alvaro Herrera 14:58
Re: pg_resetwal --next-transaction-id may cause database failed to restart. Alvaro Herrera 15:04
Re: min_safe_lsn column in pg_replication_slots view Alvaro Herrera 15:15
Re: PostgreSQL and big data - FDW Jeevan Ladhe 15:40
Re: extensible options syntax for replication parser? 📎 Robert Haas 15:51
Re: Avoiding hash join batch explosions with extreme skew and weird stats Jesse Zhang 15:55
Re: [PATCH] COPY command's data format option allows only lowercase csv, text or binary Robert Haas 16:09
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Stephen Frost 16:50
Re: PostgreSQL and big data - FDW Stephen Frost 16:53
Re: [PATCH] COPY command's data format option allows only lowercase csv, text or binary Tom Lane 16:55
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Alvaro Herrera 17:05
Re: Default setting for enable_hashagg_disk Bruce Momjian 17:08
Re: Default setting for enable_hashagg_disk Bruce Momjian 17:12
Re: xid wraparound danger due to INDEX_CLEANUP false Robert Haas 17:21
Re: Default setting for enable_hashagg_disk Tom Lane 17:29
Re: [PATCH] Incremental sort (was: PoC: Partial sort) James Coleman 17:53
Re: should libpq also require TLSv1.2 by default? Peter Eisentraut 17:57
Re: Allow CURRENT_ROLE in GRANTED BY Peter Eisentraut 18:21
Re: should libpq also require TLSv1.2 by default? Bruce Momjian 18:22
Re: Review for GetWALAvailability() Alvaro Herrera 18:27
Re: Default setting for enable_hashagg_disk Tomas Vondra 18:32
Re: Default setting for enable_hashagg_disk Tom Lane 18:40
Re: Default setting for enable_hashagg_disk Andres Freund 19:14
Re: Default setting for enable_hashagg_disk Andres Freund 19:19
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Robert Haas 19:20
Re: Default setting for enable_hashagg_disk Robert Haas 19:28
Re: Default setting for enable_hashagg_disk Andres Freund 19:31
Re: Why forbid "INSERT INTO t () VALUES ();" Fabien COELHO 19:34
Re: Default setting for enable_hashagg_disk Andres Freund 19:36
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Alvaro Herrera 19:41
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Dave Cramer 19:50
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Andres Freund 19:52
Re: Why forbid "INSERT INTO t () VALUES ();" Tom Lane 19:54
Re: xid wraparound danger due to INDEX_CLEANUP false Peter Geoghegan 20:02
Re: Default setting for enable_hashagg_disk Tomas Vondra 21:02
Re: Allow CURRENT_ROLE in GRANTED BY Alvaro Herrera 21:08
Strange behavior with polygon and NaN Jesse Zhang 22:11
Re: should libpq also require TLSv1.2 by default? Daniel Gustafsson 22:30
Re: Why forbid "INSERT INTO t () VALUES ();" Dagfinn Ilmari Mannsåker 22:31
Re: Why forbid "INSERT INTO t () VALUES ();" David G. Johnston 23:03
Re: Default setting for enable_hashagg_disk Bruce Momjian 23:15
Re: Default setting for enable_hashagg_disk Bruce Momjian 23:18
Re: Default setting for enable_hashagg_disk Bruce Momjian 23:38

June 25, 2020

Thread Author Time
Re: hashagg slowdown due to spill changes 📎 Melanie Plageman 00:26
Re: [PATCH] Initial progress reporting for COPY command vignesh C 01:05
Re: should libpq also require TLSv1.2 by default? Michael Paquier 01:50
Keep elog(ERROR) and ereport(ERROR) calls in the cold path 📎 David Rowley 01:50
Re: [PATCH] COPY command's data format option allows only lowercase csv, text or binary Michael Paquier 02:07
Re: Assertion failure in pg_copy_logical_replication_slot() Fujii Masao 02:16
Re: should libpq also require TLSv1.2 by default? Tom Lane 02:50
Re: Parallel copy 📎 Bharath Rupireddy 03:00
Re: Review for GetWALAvailability() Fujii Masao 03:34
Re: Review for GetWALAvailability() Alvaro Herrera 03:57
Re: should libpq also require TLSv1.2 by default? Michael Paquier 04:41
Re: Why forbid "INSERT INTO t () VALUES ();" Fabien COELHO 04:56
Re: Review for GetWALAvailability() Fujii Masao 05:35
Re: archive status ".ready" files may be created too early 📎 Kyotaro Horiguchi 06:35
Re: some more pg_dump refactoring Fabien COELHO 06:58
RE: PostgreSQL and big data - FDW ROS Didier 07:02
Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions? 📎 Daniel Gustafsson 07:38
Missing some ifndef FRONTEND at the top of logging.c and file_utils.c 📎 Michael Paquier 08:07
Re: Review for GetWALAvailability() 📎 Kyotaro Horiguchi 08:28
Re: Why forbid "INSERT INTO t () VALUES ();" Vik Fearing 08:39
Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...) 📎 Amit Kapila 09:01
Re: hashagg slowdown due to spill changes Tomas Vondra 09:10
Re: Missing some ifndef FRONTEND at the top of logging.c and file_utils.c Daniel Gustafsson 09:15
Open Item: Should non-text EXPLAIN always show properties? 📎 David Rowley 09:15
Re: Why forbid "INSERT INTO t () VALUES ();" David Rowley 09:27
Re: Online checksums patch - once again 📎 Daniel Gustafsson 09:43
CUBE_MAX_DIM Devrim Gündüz 10:00
Re: min_safe_lsn column in pg_replication_slots view Amit Kapila 10:20
Re: Resetting spilled txn statistics in pg_stat_replication Amit Kapila 10:35
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Robert Haas 11:56
Re: Open Item: Should non-text EXPLAIN always show properties? James Coleman 12:41
Re: More tzdb fun: POSIXRULES is being deprecated upstream Peter Eisentraut 13:08
Re: Removal of currtid()/currtid2() and some table AM cleanup Inoue, Hiroshi 13:14
Re: CUBE_MAX_DIM Darafei Komяpa Praliaskouski 13:31
Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions 📎 Dilip Kumar 13:40
Re: xid wraparound danger due to INDEX_CLEANUP false Masahiko Sawada 13:59
Re: Why forbid "INSERT INTO t () VALUES ();" Fabien COELHO 14:00
Re: More tzdb fun: POSIXRULES is being deprecated upstream Tom Lane 14:13
Re: improving basebackup.c's file-reading code Daniel Gustafsson 14:29
Re: Why forbid "INSERT INTO t () VALUES ();" Robert Haas 14:51
Re: improving basebackup.c's file-reading code Robert Haas 14:54
Re: CUBE_MAX_DIM Tom Lane 15:03
Re: min_safe_lsn column in pg_replication_slots view Alvaro Herrera 15:24
Remove a redundant condition check 📎 Ádám Balogh 15:27
Re: xid wraparound danger due to INDEX_CLEANUP false Robert Haas 15:28
Re: Parallel Seq Scan vs kernel read ahead Robert Haas 15:33
Re: Open Item: Should non-text EXPLAIN always show properties? Robert Haas 15:34
Re: PostgreSQL and big data - FDW Bruce Momjian 15:36
Re: Support for NSS as a libpq TLS backend 📎 Daniel Gustafsson 15:39
Re: Default setting for enable_hashagg_disk Robert Haas 15:46
Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path Robert Haas 15:53
Re: Why forbid "INSERT INTO t () VALUES ();" Tom Lane 16:07
Re: Default setting for enable_hashagg_disk Jeff Davis 16:14
Re: Default setting for enable_hashagg_disk Jeff Davis 16:24
Re: CUBE_MAX_DIM Alastair McKinley 16:31
Re: Open Item: Should non-text EXPLAIN always show properties? Tom Lane 16:33
Re: Why forbid "INSERT INTO t () VALUES ();" Isaac Morland 16:35
Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path Andres Freund 16:35
Re: Default setting for enable_hashagg_disk Andres Freund 16:37
Re: Default setting for enable_hashagg_disk Jeff Davis 16:42
Re: CUBE_MAX_DIM Tom Lane 16:43
Re: Weird failures on lorikeet Alvaro Herrera 16:52
Re: Default setting for enable_hashagg_disk Jeff Davis 17:15
Re: Default setting for enable_hashagg_disk Bruce Momjian 17:17
Re: [patch] demote 📎 Jehan-Guillaume de Rorthais 17:27
Re: Default setting for enable_hashagg_disk Jeff Davis 17:44
Re: Default setting for enable_hashagg_disk Robert Haas 17:47
Re: Default setting for enable_hashagg_disk Jeff Davis 18:02
Re: Default setting for enable_hashagg_disk Jeff Davis 18:10
Re: Default setting for enable_hashagg_disk Andres Freund 18:16
Re: Default setting for enable_hashagg_disk Bruce Momjian 18:25
Re: Weird failures on lorikeet Andrew Dunstan 18:42
Re: Why forbid "INSERT INTO t () VALUES ();" Robert Haas 19:06
Re: Failures with installcheck and low work_mem value in 13~ Peter Geoghegan 19:15
Re: Default setting for enable_hashagg_disk Bruce Momjian 19:24
Re: Open Item: Should non-text EXPLAIN always show properties? James Coleman 19:29
Re: should libpq also require TLSv1.2 by default? Robert Haas 19:41
Re: Open Item: Should non-text EXPLAIN always show properties? Tom Lane 19:46
Re: Default setting for enable_hashagg_disk Bruce Momjian 19:56
Re: should libpq also require TLSv1.2 by default? Tom Lane 19:57
Re: Default setting for enable_hashagg_disk Andres Freund 20:36
Re: CUBE_MAX_DIM Alastair McKinley 20:47
Re: Default setting for enable_hashagg_disk Jeff Davis 21:28
Re: Avoiding hash join batch explosions with extreme skew and weird stats 📎 Melanie Plageman 22:09
Re: create database with template doesn't copy database ACL Bruce Momjian 22:23
Re: should libpq also require TLSv1.2 by default? Tom Lane 22:44
Re: Default setting for enable_hashagg_disk Alvaro Herrera 22:44
Re: Default setting for enable_hashagg_disk Andres Freund 22:48
Re: min_safe_lsn column in pg_replication_slots view Michael Paquier 22:53
Re: should libpq also require TLSv1.2 by default? Bruce Momjian 22:55
Re: Default setting for enable_hashagg_disk Alvaro Herrera 22:58
Re: Default setting for enable_hashagg_disk Tomas Vondra 23:11
Re: Default setting for enable_hashagg_disk Tomas Vondra 23:18
Re: Default setting for enable_hashagg_disk Tomas Vondra 23:23
Re: min_safe_lsn column in pg_replication_slots view Alvaro Herrera 23:24
Re: Enabling B-Tree deduplication by default Peter Geoghegan 23:28
Re: Default setting for enable_hashagg_disk Tomas Vondra 23:53

June 26, 2020

Thread Author Time
Re: xid wraparound danger due to INDEX_CLEANUP false Peter Geoghegan 00:18
Re: Avoiding hash join batch explosions with extreme skew and weird stats Tomas Vondra 00:22
Re: xid wraparound danger due to INDEX_CLEANUP false Peter Geoghegan 00:44
Re: Missing some ifndef FRONTEND at the top of logging.c and file_utils.c Michael Paquier 00:59
Re: Failures with installcheck and low work_mem value in 13~ Michael Paquier 01:03
Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path David Rowley 01:21

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