public inbox for [email protected]help / color / mirror / Atom feed
Messages from [email protected] Re: Horribly slow pg_upgrade performance with many Large Objects 2025-04-08 21:37 UTC Jan Wieck <[email protected]> Re: TOAST versus toast 2025-03-17 15:27 UTC Jan Wieck <[email protected]> Re: TOAST versus toast 2025-03-17 03:37 UTC Jan Wieck <[email protected]> Re: transaction lost when delete clog file after normal shutdown 2024-12-23 18:06 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-14 13:50 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-12 16:40 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-12 15:12 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-12 14:45 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-12 13:51 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-07 20:05 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-07 16:09 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-06 19:22 UTC Jan Wieck <[email protected]> Re: Commit Timestamp and LSN Inversion issue 2024-11-05 13:58 UTC Jan Wieck <[email protected]> Re: Track the amount of time waiting due to cost_delay 2024-06-11 17:26 UTC Jan Wieck <[email protected]> Re: Named Prepared statement problems and possible solutions 2023-06-08 21:16 UTC Jan Wieck <[email protected]> Re: Named Prepared statement problems and possible solutions 2023-06-08 19:49 UTC Jan Wieck <[email protected]> Re: Named Prepared statement problems and possible solutions 2023-06-08 15:15 UTC Jan Wieck <[email protected]> Re: Named Prepared statement problems and possible solutions 2023-06-08 14:31 UTC Jan Wieck <[email protected]> Re: Named Prepared statement problems and possible solutions 2023-06-08 13:53 UTC Jan Wieck <[email protected]> Re: Named Prepared statement problems and possible solutions 2023-06-08 12:43 UTC Jan Wieck <[email protected]> Re: PL/pgSQL cursors should get generated portal names by default 2022-11-07 21:54 UTC Jan Wieck <[email protected]> Re: PL/pgSQL cursors should get generated portal names by default 2022-11-07 16:10 UTC Jan Wieck <[email protected]> Re: PL/pgSQL cursors should get generated portal names by default 2022-11-04 23:19 UTC Jan Wieck <[email protected]> Re: Limiting memory allocation 2022-05-23 12:59 UTC Jan Wieck <[email protected]> Re: Limiting memory allocation 2022-05-18 15:41 UTC Jan Wieck <[email protected]> Re: Limiting memory allocation 2022-05-18 14:23 UTC Jan Wieck <[email protected]> Re: Limiting memory allocation 2022-05-17 20:10 UTC Jan Wieck <[email protected]> Re: Change the csv log to 'key:value' to facilitate the user to understanding and processing of logs 2022-03-15 14:33 UTC Jan Wieck <[email protected]> Re: should we enable log_checkpoints out of the box? 2021-11-05 15:36 UTC Jan Wieck <[email protected]> Re: should we enable log_checkpoints out of the box? 2021-11-03 17:43 UTC Jan Wieck <[email protected]> Re: should we enable log_checkpoints out of the box? 2021-11-03 03:18 UTC Jan Wieck <[email protected]> Re: should we enable log_checkpoints out of the box? 2021-11-02 18:19 UTC Jan Wieck <[email protected]> Re: should we enable log_checkpoints out of the box? 2021-10-31 20:38 UTC Jan Wieck <[email protected]> Re: PostgreSQL High Precision Support Extension. 2021-09-21 22:47 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-30 17:28 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-30 16:44 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-30 16:43 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-29 18:14 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-29 16:55 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-29 16:28 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-29 15:46 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-15 23:18 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-15 18:14 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-15 16:58 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-15 16:38 UTC Jan Wieck <[email protected]> Re: pg_upgrade does not upgrade pg_stat_statements properly 2021-07-15 16:35 UTC Jan Wieck <[email protected]> Re: AWS forcing PG upgrade from v9.6 a disaster 2021-05-29 11:39 UTC Jan Wieck <[email protected]> Re: AWS forcing PG upgrade from v9.6 a disaster 2021-05-29 02:27 UTC Jan Wieck <[email protected]> Re: AWS forcing PG upgrade from v9.6 a disaster 2021-05-28 20:23 UTC Jan Wieck <[email protected]> Re: Always bump PG_CONTROL_VERSION? 2021-05-13 22:59 UTC Jan Wieck <[email protected]> Re: Always bump PG_CONTROL_VERSION? 2021-05-13 21:42 UTC Jan Wieck <[email protected]> Re: SELECT INTO deprecation 2021-03-30 19:05 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-24 16:05 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-24 16:04 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-23 19:59 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-23 19:22 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-23 18:54 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-23 18:23 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-23 17:25 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-23 12:51 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-22 23:18 UTC Jan Wieck <[email protected]> Re: Fix pg_upgrade to preserve datdba 2021-03-22 18:07 UTC Jan Wieck <[email protected]> Re: Fix pg_upgrade to preserve datdba 2021-03-21 19:36 UTC Jan Wieck <[email protected]> Re: Fix pg_upgrade to preserve datdba 2021-03-21 17:50 UTC Jan Wieck <[email protected]> Re: Fix pg_upgrade to preserve datdba 2021-03-21 17:15 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-21 16:56 UTC Jan Wieck <[email protected]> Fix pg_upgrade to preserve datdba (was: Re: pg_upgrade failing for 200+ million Large Objects) 2021-03-21 16:50 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-20 16:55 UTC Jan Wieck <[email protected]> Re: pg_upgrade failing for 200+ million Large Objects 2021-03-20 04:39 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-03-05 01:38 UTC Jan Wieck <[email protected]> Re: PROXY protocol support 2021-03-04 21:01 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-03-04 20:55 UTC Jan Wieck <[email protected]> Re: PROXY protocol support 2021-03-04 20:29 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-24 15:46 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-22 19:00 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-22 16:44 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-22 15:01 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-22 14:55 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-19 18:30 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-19 15:13 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-19 13:46 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-18 16:01 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-02-10 21:32 UTC Jan Wieck <[email protected]> Re: Extensibility of the PostgreSQL wire protocol 2021-01-25 17:17 UTC Jan Wieck <[email protected]> Extensibility of the PostgreSQL wire protocol 2021-01-25 15:07 UTC Jan Wieck <[email protected]> Re: Performance improvement of WAL writing? 2019-08-28 11:12 UTC Jan Wieck <[email protected]> Re: lazy detoasting 2018-04-11 02:17 UTC Jan Wieck <[email protected]> Re: DO with a large amount of statements get stuck with high memory consumption 2016-07-18 14:37 UTC Jan Wieck <[email protected]> Re: DO with a large amount of statements get stuck with high memory consumption 2016-07-18 13:59 UTC Jan Wieck <[email protected]> Re: One process per session lack of sharing 2016-07-18 02:00 UTC Jan Wieck <[email protected]> Re: DO with a large amount of statements get stuck with high memory consumption 2016-07-17 23:35 UTC Jan Wieck <[email protected]> Re: A Modest Upgrade Proposal 2016-07-17 18:55 UTC Jan Wieck <[email protected]> Re: One process per session lack of sharing 2016-07-17 13:29 UTC Jan Wieck <[email protected]> Re: DO with a large amount of statements get stuck with high memory consumption 2016-07-16 19:47 UTC Jan Wieck <[email protected]> Re: WAL Re-Writes 2016-01-31 21:26 UTC Jan Wieck <[email protected]> Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. 2015-09-25 14:20 UTC Jan Wieck <[email protected]> Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. 2015-09-18 02:01 UTC Jan Wieck <[email protected]> Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. 2015-09-15 16:02 UTC Jan Wieck <[email protected]> Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. 2015-09-15 15:35 UTC Jan Wieck <[email protected]> Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. 2015-09-15 14:42 UTC Jan Wieck <[email protected]> Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. 2015-09-15 13:25 UTC Jan Wieck <[email protected]> Re: Double linking MemoryContext children 2015-09-14 12:24 UTC Jan Wieck <[email protected]> Re: Double linking MemoryContext children 2015-09-11 15:13 UTC Jan Wieck <[email protected]> Re: Double linking MemoryContext children 2015-09-11 13:52 UTC Jan Wieck <[email protected]> Double linking MemoryContext children 2015-09-11 13:33 UTC Jan Wieck <[email protected]> Re: Small patch to fix an O(N^2) problem in foreign keys 2015-09-10 12:57 UTC Jan Wieck <[email protected]> Small patch to fix an O(N^2) problem in foreign keys 2015-09-03 22:42 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-14 13:52 UTC Jan Wieck <[email protected]> Re: DBT-3 with SF=20 got failed 2015-06-11 14:20 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-10 15:51 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-10 15:12 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-10 15:03 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-10 14:54 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-10 14:18 UTC Jan Wieck <[email protected]> Re: s_lock() seems too aggressive for machines with many sockets 2015-06-10 13:54 UTC Jan Wieck <[email protected]> s_lock() seems too aggressive for machines with many sockets 2015-06-10 13:18 UTC Jan Wieck <[email protected]> Re: Possible problem with pgcrypto 2015-02-06 13:49 UTC Jan Wieck <[email protected]> Re: Possible problem with pgcrypto 2015-02-05 19:15 UTC Jan Wieck <[email protected]> Re: Possible problem with pgcrypto 2015-02-05 19:10 UTC Jan Wieck <[email protected]> Possible problem with pgcrypto 2015-02-05 15:48 UTC Jan Wieck <[email protected]> Moving of INT64_FORMAT to c.h 2014-10-16 12:04 UTC Jan Wieck <[email protected]> Re: DDL Damage Assessment 2014-10-02 22:43 UTC Jan Wieck <[email protected]> Re: pg_receivexlog and replication slots 2014-10-01 17:36 UTC Jan Wieck <[email protected]> Re: pg_receivexlog and replication slots 2014-10-01 17:22 UTC Jan Wieck <[email protected]> Re: pg_receivexlog and replication slots 2014-10-01 17:17 UTC Jan Wieck <[email protected]> Re: jsonb format is pessimal for toast compression 2014-09-24 05:02 UTC Jan Wieck <[email protected]> Re: proposal: plpgsql - Assert statement 2014-09-18 00:40 UTC Jan Wieck <[email protected]> Re: proposal: plpgsql - Assert statement 2014-09-14 18:49 UTC Jan Wieck <[email protected]> Re: pgbench throttling latency limit 2014-09-10 18:49 UTC Jan Wieck <[email protected]> Re: Improving PL/PgSQL 2014-09-06 18:57 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-06 17:11 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-06 16:37 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-06 16:31 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 1.2 2014-09-06 16:12 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-06 16:06 UTC Jan Wieck <[email protected]> Re: pgbench throttling latency limit 2014-09-05 15:38 UTC Jan Wieck <[email protected]> Re: pgbench throttling latency limit 2014-09-05 12:59 UTC Jan Wieck <[email protected]> Re: proposal: plpgsql - Assert statement 2014-09-05 12:35 UTC Jan Wieck <[email protected]> Re: jsonb format is pessimal for toast compression 2014-09-05 02:26 UTC Jan Wieck <[email protected]> Re: jsonb format is pessimal for toast compression 2014-09-05 02:24 UTC Jan Wieck <[email protected]> Re: jsonb format is pessimal for toast compression 2014-09-05 02:04 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 1.2 2014-09-04 15:45 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 1.2 2014-09-04 13:38 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 1.2 2014-09-04 13:24 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-03 14:24 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 23:08 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 22:50 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 21:47 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 21:43 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 21:32 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 21:23 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 21:20 UTC Jan Wieck <[email protected]> Re: PL/pgSQL 2 2014-09-02 21:08 UTC Jan Wieck <[email protected]> Re: How can we make beta testing better? 2014-04-17 21:31 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-13 21:46 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-13 18:22 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-12 18:10 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-12 15:41 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-12 15:15 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-12 12:42 UTC Jan Wieck <[email protected]> Re: Problem with txid_snapshot_in/out() functionality 2014-04-12 12:34 UTC Jan Wieck <[email protected]> Problem with txid_snapshot_in/out() functionality 2014-04-11 21:07 UTC Jan Wieck <[email protected]> 162+ results
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox