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

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Sachin Divekar <ssd532(at)gmail(dot)com>
Cc: MichaelDBA <MichaelDBA(at)sqlexec(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:58:02
Message-ID: CAHOFxGow_ZyFs-kqVYUx--BJkDR-P5Wnn_60672wpcqfMxkeAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Dec 3, 2019 at 11:46 AM Sachin Divekar <ssd532(at)gmail(dot)com> wrote:

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

I am not aware of any. Either you use it because it fits your need, or not.

Note- please don't top-post (reply and include all the previous
conversation below) on the Postgres mailing lists. Quote only the part(s)
you are responding to and reply there.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Andres Freund 2019-12-03 21:13:21 Re: performance degredation after upgrade from 9.6 to 12
Previous Message Sachin Divekar 2019-12-03 18:45:53 Re: Make recently inserted/updated records available in the buffer/cache