Re: Make recently inserted/updated records available in the buffer/cache
| От | Sachin Divekar |
|---|---|
| Тема | Re: Make recently inserted/updated records available in the buffer/cache |
| Дата | |
| Msg-id | CA+A8H7nb1J2Aak=qUfqsGP=UNwj6iUur8hPTOkNTTBrQxSSGYw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Make recently inserted/updated records available in thebuffer/cache (MichaelDBA <MichaelDBA@sqlexec.com>) |
| Ответы |
Re: Make recently inserted/updated records available in the buffer/cache
|
| Список | 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@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 по дате отправления: