pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Jason McLaurin <jason@jcore.io>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Very slow queries followed by checkpointer process killed with signal 9
Date: Mon, 3 Apr 2023 08:33:19 -0400
Message-ID: <c17da59d-0845-cac7-d1d9-486b46cf0427@joeconway.com> (raw)
In-Reply-To: <1090044.1680486018@sss.pgh.pa.us>
References: <CAJN0UCS1xhx11YMVXua4LkyDYmLbJWF0dUwcasjhWGcHCvBCbQ@mail.gmail.com>
	<1077329.1680479022@sss.pgh.pa.us>
	<CAJN0UCSqDfQpS-xsiMj4BdSUOS0iyFWo8-Xs+4UN-GFY8ucnZQ@mail.gmail.com>
	<1090044.1680486018@sss.pgh.pa.us>

On 4/2/23 21:40, Tom Lane wrote:
> Jason McLaurin <jason@jcore.io> writes:
>> Is there anywhere you'd suggest we start looking for hints? I'd be
>> interested in increasing relevant logging verbosity so that we can see when
>> key background processes are running, both in Postgres core and Timescale.
> 
> It might be helpful to try to identify which wait events the slow
> queries are blocking on (pg_stat_activity.wait_event_type and
> .wait_event).  I'm not sure if you're going to be able to extract
> useful data, because your query on pg_stat_activity is likely to
> be slow too.  But it's a place to start.
> 
> Also, given that you're evidently incurring the wrath of the OOM
> killer, you should try to understand why the kernel thinks it's
> under memory pressure.  Do you have too many processes, or perhaps
> you've configured too much shared memory?

Given this:

> This is Postgres 14.5 running in the TimescaleDB Docker image.

Possibly the docker image is running with a cgroup memory.limit set?

The OOM killer will trigger on any cgroup limit even if the host has 
plenty of free memory.


-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com






view thread (6+ messages)  latest in thread

Message-ID: <c17da59d-0845-cac7-d1d9-486b46cf0427@joeconway.com>
Permalink:  ../c17da59d-0845-cac7-d1d9-486b46cf0427@joeconway.com/
Also on:    postgresql.org/message-id/c17da59d-0845-cac7-d1d9-486b46cf0427@joeconway.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: mail@joeconway.com, tgl@sss.pgh.pa.us, jason@jcore.io
  Subject: Re: Very slow queries followed by checkpointer process killed with signal 9
  In-Reply-To: <c17da59d-0845-cac7-d1d9-486b46cf0427@joeconway.com>
  References: <CAJN0UCS1xhx11YMVXua4LkyDYmLbJWF0dUwcasjhWGcHCvBCbQ@mail.gmail.com> <1077329.1680479022@sss.pgh.pa.us> <CAJN0UCSqDfQpS-xsiMj4BdSUOS0iyFWo8-Xs+4UN-GFY8ucnZQ@mail.gmail.com> <1090044.1680486018@sss.pgh.pa.us> <c17da59d-0845-cac7-d1d9-486b46cf0427@joeconway.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox