| From: | Sachin Divekar <ssd532(at)gmail(dot)com> |
|---|---|
| To: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
| Cc: | Michael Lewis <mlewis(at)entrata(dot)com>, Hüseyin Demir <demirhuseyinn(dot)94(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 18:45:53 |
| Message-ID: | CA+A8H7nb1J2Aak=qUfqsGP=UNwj6iUur8hPTOkNTTBrQxSSGYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)sqlexec(dot)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.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2019-12-03 18:58:02 | Re: Make recently inserted/updated records available in the buffer/cache |
| Previous Message | MichaelDBA | 2019-12-03 17:32:48 | Re: Make recently inserted/updated records available in the buffer/cache |