Re: Make recently inserted/updated records available in the buffer/cache

From: MichaelDBA <MichaelDBA(at)sqlexec(dot)com>
To: Michael Lewis <mlewis(at)entrata(dot)com>
Cc: Hüseyin Demir <demirhuseyinn(dot)94(at)gmail(dot)com>, Sachin Divekar <ssd532(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Make recently inserted/updated records available in the buffer/cache
Date: 2019-12-03 17:32:48
Message-ID: 33edd9ba-5ab8-f7d1-6376-4046f9ba6d9f@sqlexec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Yep, I concur completely!  For tables treated like queues you gotta do
this stuff or deal with bloat and fragmented indexes.

Michael Lewis wrote on 12/3/2019 12:29 PM:
> "I am going to use it as a queue"
>
> You may want to look at lowering fillfactor if this queue is going to
> have frequent updates, and also make autovacuum/analyze much more
> aggressive assuming many updates and deletes.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Sachin Divekar 2019-12-03 18:45:53 Re: Make recently inserted/updated records available in the buffer/cache
Previous Message Michael Lewis 2019-12-03 17:29:18 Re: Make recently inserted/updated records available in the buffer/cache