Horton
Menu

Maxim Boguk

maxim.boguk@gmail.com

Email: maxim.boguk@gmail.com
Name: Maxim Boguk
Messages: 270
First message: 2009-07-31
Last message: 2026-06-22

Recent messages

DateSubject
2026-06-22T20:22:53Z Re: BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
2026-06-02T18:51:43Z Re: BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
2025-07-02T07:04:12Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02T06:35:21Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02T00:03:00Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-05-14T00:47:30Z Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2025-05-12T17:55:07Z Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2025-05-12T15:18:43Z Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2025-05-12T14:21:09Z Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2025-05-12T14:04:45Z Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2025-05-12T13:08:09Z Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2025-05-12T11:49:10Z inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
2024-10-14T12:33:03Z Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-08T13:08:54Z Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-04T14:07:26Z Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-04T13:57:59Z Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-08-25T20:31:44Z Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22T21:37:05Z Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22T21:16:17Z Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22T20:27:24Z Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22T17:05:50Z Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22T16:41:37Z Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-03-12T10:40:31Z Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2023-09-01T18:01:26Z Re: Index bloat and REINDEX/VACUUM optimization for partial index
2023-08-31T15:05:41Z Re: Index bloat and REINDEX/VACUUM optimization for partial index
2023-05-01T04:46:02Z Re: BUG #17913: alter column set (n_distinct=...) on partition head doesn't work for declarative partitioned tables
2023-04-21T09:13:32Z Unexpectedly huge memory usage (over 180x of work_mem) during hash join... confirmed by TopMemoryContext results (postgresql 13.10)
2023-04-05T00:30:17Z Re: BUG #17885: slow planning constraint_exclusion
2023-03-31T12:40:59Z Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28T06:34:32Z Re: BUG #17870: Analyze on remote postgresql_fdw table never finish
2023-03-28T06:28:04Z Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28T06:21:54Z Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28T04:54:04Z Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28T02:27:51Z Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-01-05T11:44:33Z Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2023-01-05T10:57:00Z Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2023-01-01T17:06:49Z Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2023-01-01T16:51:07Z Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2023-01-01T16:30:55Z Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2023-01-01T11:34:50Z Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2022-12-31T12:26:08Z How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
2022-09-09T21:05:27Z Re: Missing query plan for auto_explain.
2022-09-05T23:28:57Z Re: Missing query plan for auto_explain.
2022-08-26T08:04:12Z Re: BUG #17594: conditional hash indexes size (hash index ignore WHERE condition during CREATE INDEX?)
2022-08-16T08:34:14Z Re: BUG #17586: Look like there are an another bug in REINDEX INDEX CONCURRENTLY of pg_toast indexes
2022-08-09T23:27:49Z Re: BUG #17574: Attaching an invalid index to partition head make head index invalid forever
2022-05-09T16:24:22Z Re: BUG #17478: Missing documents in the index after CREATE INDEX CONCURRENTLY (but existing in the table)
2022-02-02T09:24:42Z Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-29T15:23:49Z Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-28T14:17:28Z Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table