Filter:

Messages in May 2021

Threads68 messages
7Started
4Replied in own
57Replied to othersin 14 threads
Patchesof which 2 carried a patch
1New patchfirst in its thread
1Follow-uprevision of an earlier one
ActivityThreadSent
Started threadANALYZE's dead tuple accounting can get confusedabout 5 years ago
Replied (own)Follow-up patchTeaching users how they can get the most out of HOT in Postgres 14about 5 years ago
Started threadpgsql: Fix VACUUM VERBOSE's LP_DEAD item pages output.about 5 years ago
Replied (other)Move pg_attribute.attcompression to earlier in struct for reduced size?about 5 years ago
Replied (other)Move pg_attribute.attcompression to earlier in struct for reduced size?about 5 years ago
Replied (other)Decoding speculative insert with toast leaks memoryabout 5 years ago
Replied (other)Testing autovacuum wraparound (including failsafe)about 5 years ago
Started threadpgsql: Consider triggering VACUUM failsafe during scan.about 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)BUG #17017: Two versions of the same row of records are returned in one queryabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)Less selective index chosen unexpectedlyabout 5 years ago
Replied (other)Less selective index chosen unexpectedlyabout 5 years ago
Replied (own)Teaching users how they can get the most out of HOT in Postgres 14about 5 years ago
Replied (other)Lowering the ever-growing heap->pd_lowerabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)Testing autovacuum wraparound (including failsafe)about 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)BUG #16833: postgresql 13.1 process crash every hourabout 5 years ago
Replied (other)prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619about 5 years ago
Replied (other)BUG #16833: postgresql 13.1 process crash every hourabout 5 years ago
Started threadpgsql: Harden nbtree deduplication posting split code.about 5 years ago
Started threadpgsql: Harden nbtree deduplication posting split code.about 5 years ago
Replied (other)BUG #16833: postgresql 13.1 process crash every hourabout 5 years ago
Replied (other)BUG #16833: postgresql 13.1 process crash every hourabout 5 years ago
Replied (own)Teaching users how they can get the most out of HOT in Postgres 14about 5 years ago
Replied (other)First patchTesting autovacuum wraparound (including failsafe)about 5 years ago
Started threadpgsql: Fix autovacuum log output heap truncation issue.about 5 years ago
Replied (own)Teaching users how they can get the most out of HOT in Postgres 14about 5 years ago
Replied (other)Performance degradation of REFRESH MATERIALIZED VIEWabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)PG 14 release notes, first draftabout 5 years ago
Replied (other)Processing btree walks as a batch to parallelize IOabout 5 years ago
Replied (other)[BUG]"FailedAssertion" reported in lazy_scan_heap() when running logical replicationabout 5 years ago
Replied (other)[BUG]"FailedAssertion" reported in lazy_scan_heap() when running logical replicationabout 5 years ago
Started threadpgsql: Remove overzealous VACUUM visibility map assertion.about 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)MaxOffsetNumber for Table AMsabout 5 years ago
Replied (other)RFE: Make statistics robust for unplanned eventsabout 5 years ago