Re: Huge shared hit for small table - Mailing list pgsql-performance

From Scott Rankin
Subject Re: Huge shared hit for small table
Date
Msg-id D6F15B3F-A4CB-4BDD-AC08-3FABC81D4404@motus.com
Whole thread Raw
In response to Re: Huge shared hit for small table  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-performance
I think we have a winner.  I looked in and found a process that was 'idle in transaction' for a couple days - and once
Ikilled it, query performance went back to normal.
 

Thank you all for the very quick responses on this.

On 11/4/19, 3:41 PM, "Peter Geoghegan" <pg@bowt.ie> wrote:

    On Mon, Nov 4, 2019 at 12:38 PM Scott Rankin <srankin@motus.com> wrote:
    > Definitely no long-running transactions on this table; in fact, this table is pretty infrequently updated – on
theorder of a few tens of rows updated per day.
 

    But a long running transaction will have an impact on all tables --
    not just the tables that happen to have been accessed so far in the
    long running transaction. This is necessary because nothing stops the
    long running transaction from SELECTing data from any table at any
    time -- we need to pessimistically keep around the data required to
    make that work.

    --
    Peter Geoghegan



This email message contains information that Motus, LLC considers confidential and/or proprietary, or may later
designateas confidential and proprietary. It is intended only for use of the individual or entity named above and
shouldnot be forwarded to any other persons or entities without the express consent of Motus, LLC, nor should it be
usedfor any purpose other than in the course of any potential or actual business relationship with Motus, LLC. If the
readerof this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended
recipient,you are hereby notified that any dissemination, distribution, or copying of this communication is strictly
prohibited.If you have received this communication in error, please notify sender immediately and destroy the original
message.

Internal Revenue Service regulations require that certain types of written advice include a disclaimer. To the extent
thepreceding message contains advice relating to a Federal tax issue, unless expressly stated otherwise the advice is
notintended or written to be used, and it cannot be used by the recipient or any other taxpayer, for the purpose of
avoidingFederal tax penalties, and was not written to support the promotion or marketing of any transaction or matter
discussedherein.
 

pgsql-performance by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Huge shared hit for small table
Next
From: Jeff Janes
Date:
Subject: Re: Huge shared hit for small table