Postgres Pro
Downloads
Home   >   mailing lists

Re: Make recently inserted/updated records available in the buffer/cache - Mailing list pgsql-performance

From Sachin Divekar
Subject Re: Make recently inserted/updated records available in the buffer/cache
Date
Msg-id CA+A8H7nb1J2Aak=qUfqsGP=UNwj6iUur8hPTOkNTTBrQxSSGYw@mail.gmail.com
Whole thread Raw
In response to Re: Make recently inserted/updated records available in thebuffer/cache  (MichaelDBA <MichaelDBA@sqlexec.com>)
Responses Re: Make recently inserted/updated records available in the buffer/cache  (Michael Lewis <mlewis@entrata.com>)
List pgsql-performance
Tree view
Thank you, Michaels.
.
I didn't know about fillfactor and table bloat. Did some reading on those topics. We will definitely need to tweak these settings. 

I am also going to use SKIP LOCKED to _select for update_. Any suggestions on tuning parameters for SKIP LOCKED?

Thanks

On Tue, Dec 3, 2019 at 11:02 PM MichaelDBA <MichaelDBA@sqlexec.com> wrote:
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.

pgsql-performance by date:

Previous
From: MichaelDBA
Date:
Subject: Re: Make recently inserted/updated records available in thebuffer/cache
Next
From: Michael Lewis
Date:
Subject: Re: Make recently inserted/updated records available in the buffer/cache