[HN Gopher] Optimizing Postgres's autovacuum for high-churn tables
       ___________________________________________________________________
        
       Optimizing Postgres's autovacuum for high-churn tables
        
       Author : chuckhend
       Score  : 23 points
       Date   : 2023-09-01 16:29 UTC (6 hours ago)
        
 (HTM) web link (tembo.io)
 (TXT) w3m dump (tembo.io)
        
       | abalashov wrote:
       | Very helpful article! It jives with the evolution of my own
       | understanding of autovacuum tuning over a decade and a half of
       | writing high-performance Postgres-backed VoIP routing systems.
       | 
       | I would add to this that if you truly have a high-churn table,
       | perhaps a traditional RDBM is not the best choice. Ask me how I
       | learned that lesson the hard way. There are many things that, in
       | hindsight, really should have gone into ELK or Splunk or Redis or
       | something more suited to ephemeral or short-lived data sets that
       | also turn over constantly.
       | 
       | But, sometimes there is no choice, or the churn is high but not
       | quite high enough to rule out the use of an RDBM altogether. For
       | those scenarios, the tips in this article really shine.
        
         | sophacles wrote:
         | How'd you learn that lesson the hard way?
        
       ___________________________________________________________________
       (page generated 2023-09-01 23:01 UTC)