Filter:

Messages on October 03, 2023

20 messages12 started threads2 replied (own)6 replied (other)5 other threads0 first patch1 follow-up patch
ActivityThreadSent
Replied (other)Add support for AT LOCALover 2 years ago
Replied (other)Add a new BGWORKER_BYPASS_ROLELOGINCHECK flagover 2 years ago
Replied (other)[PGDOCS] Inconsistent linkends to "monitoring" views.over 2 years ago
Replied (own)Follow-up patchIncorrect handling of OOM in WAL replay leading to data lossover 2 years ago
Replied (other)How to force "re-TOAST" after changing STORAGE or COMPRESSION?over 2 years ago
Replied (other)pg_stat_get_activity(): integer overflow due to (int) * (int) for MemoryContextAllocHuge()over 2 years ago
Replied (own)Fail hard if xlogreader.c fails on out-of-memoryover 2 years ago
Started threadpgsql: Avoid memory size overflow when allocating backend activity buffover 2 years ago
Started threadpgsql: Avoid memory size overflow when allocating backend activity buffover 2 years ago
Started threadpgsql: Avoid memory size overflow when allocating backend activity buffover 2 years ago
Started threadpgsql: Avoid memory size overflow when allocating backend activity buffover 2 years ago
Started threadpgsql: Avoid memory size overflow when allocating backend activity buffover 2 years ago
Started threadpgsql: Avoid memory size overflow when allocating backend activity buffover 2 years ago
Replied (other)How to force "re-TOAST" after changing STORAGE or COMPRESSION?over 2 years ago
Started threadpgsql: Fail hard on out-of-memory failures in xlogreader.cover 2 years ago
Started threadpgsql: Fail hard on out-of-memory failures in xlogreader.cover 2 years ago
Started threadpgsql: Fail hard on out-of-memory failures in xlogreader.cover 2 years ago
Started threadpgsql: Fail hard on out-of-memory failures in xlogreader.cover 2 years ago
Started threadpgsql: Fail hard on out-of-memory failures in xlogreader.cover 2 years ago
Started threadpgsql: Fail hard on out-of-memory failures in xlogreader.cover 2 years ago