pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Purging few months old data and vacuuming in production
Date: Sat, 7 Jan 2023 07:40:01 -0600
Message-ID: <a4199207-a5dc-583a-5782-67e1ab8f57c8@gmail.com> (raw)
In-Reply-To: <20230107112946.pamp3ot44sa7aylk@hjp.at>
References: <SEZPR06MB569032257FDFACE5C906ADB4C2F09@SEZPR06MB5690.apcprd06.prod.outlook.com>
	<6f623e3a-d93d-bc89-b553-d2f87a82bd73@gmail.com>
	<SEZPR06MB56905EB1343165E6D1C8B5B4C2FB9@SEZPR06MB5690.apcprd06.prod.outlook.com>
	<1984ec34-26fa-a585-3312-ef38814b5f42@gmail.com>
	<SEZPR06MB5690F3A7AE31D9EA19DA0A28C2FB9@SEZPR06MB5690.apcprd06.prod.outlook.com>
	<90262fac-d6c7-e253-6988-a081c9e47a15@gmail.com>
	<SEZPR06MB56909FBE8EF32C717E40C210C2F89@SEZPR06MB5690.apcprd06.prod.outlook.com>
	<20230107112946.pamp3ot44sa7aylk@hjp.at>

On 1/7/23 05:29, Peter J. Holzer wrote:
[snip]
> If I understood correctly, you have to delete about 3 million records
> (worst case) from the main table each day. Including the other 8 tables
> those are 27 million DELETE queries each of which deletes only a few
> records. That's about 300 queries per second. I'd be worried about
> impacting performance on other queries at this rate.

300 *records*/second.  Fewer DELETE statements if there are one-many 
relationships with the child tables.

> I'd go for a middle ground: Instead of expiring once per day, use a
> shorter interval, maybe once per hour or once per minute. That will
> (probably) make each expire job really quick but still create much less
> load overall.

-- 
Born in Arizona, moved to Babylonia.

view thread (13+ messages)  latest in thread

Message-ID: <a4199207-a5dc-583a-5782-67e1ab8f57c8@gmail.com>
Permalink:  ../a4199207-a5dc-583a-5782-67e1ab8f57c8@gmail.com/
Also on:    postgresql.org/message-id/a4199207-a5dc-583a-5782-67e1ab8f57c8@gmail.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: ronljohnsonjr@gmail.com
  Subject: Re: Purging few months old data and vacuuming in production
  In-Reply-To: <a4199207-a5dc-583a-5782-67e1ab8f57c8@gmail.com>
  References: <SEZPR06MB569032257FDFACE5C906ADB4C2F09@SEZPR06MB5690.apcprd06.prod.outlook.com> <6f623e3a-d93d-bc89-b553-d2f87a82bd73@gmail.com> <SEZPR06MB56905EB1343165E6D1C8B5B4C2FB9@SEZPR06MB5690.apcprd06.prod.outlook.com> <1984ec34-26fa-a585-3312-ef38814b5f42@gmail.com> <SEZPR06MB5690F3A7AE31D9EA19DA0A28C2FB9@SEZPR06MB5690.apcprd06.prod.outlook.com> <90262fac-d6c7-e253-6988-a081c9e47a15@gmail.com> <SEZPR06MB56909FBE8EF32C717E40C210C2F89@SEZPR06MB5690.apcprd06.prod.outlook.com> <20230107112946.pamp3ot44sa7aylk@hjp.at> <a4199207-a5dc-583a-5782-67e1ab8f57c8@gmail.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