pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Atul Kumar <akumar14871@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: idle transactions vs memory
Date: Mon, 07 Dec 2020 09:47:46 +0100
Message-ID: <b97c85269fd11ca29d06f50a2d51757b9e9b85d7.camel@cybertec.at> (raw)
In-Reply-To: <CA+ONtZ4qAb8VSpWacOiSTOJ5-y-Pb_uhHUW_kGkO4gDMthb4Sw@mail.gmail.com>
References: <CA+ONtZ7mpJ7W43G19wATC7aipjUWqBDw1_QQdd7CARAvA7DS3w@mail.gmail.com>
	<10CEA2EF-210C-48F3-AC4C-F035292E6CAD@elevated-dev.com>
	<CA+ONtZ4qAb8VSpWacOiSTOJ5-y-Pb_uhHUW_kGkO4gDMthb4Sw@mail.gmail.com>

On Mon, 2020-12-07 at 11:04 +0530, Atul Kumar wrote:
> The transactions state is 'idle' from more than 15 minutes, so my
> question is that are they occupying any amount of RAM?
> 
> are these 'idle' transactions are using CPU ?

They are not using any CPU, and they are using very little RAM.

They make starting a query (taking a snapshot) a little slower,
but you probably won't notice that.

Their biggest danger is that there is no guarantee that they
remain idle, and if you have too many active sessions, your database
might have more work than it can handle.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com






view thread (7+ messages)

Message-ID: <b97c85269fd11ca29d06f50a2d51757b9e9b85d7.camel@cybertec.at>
Permalink:  ../b97c85269fd11ca29d06f50a2d51757b9e9b85d7.camel@cybertec.at/
Also on:    postgresql.org/message-id/b97c85269fd11ca29d06f50a2d51757b9e9b85d7.camel@cybertec.at

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: laurenz.albe@cybertec.at, akumar14871@gmail.com
  Subject: Re: idle transactions vs memory
  In-Reply-To: <b97c85269fd11ca29d06f50a2d51757b9e9b85d7.camel@cybertec.at>

* 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