Re: postgres in swap space

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: postgres in swap space
Date: 2025-11-18 00:18:36
Message-ID: CANzqJaDw_W26Gj2w9hVzJ0u4Qjrj_NxXp2XWJvaAHz24zRoRaA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 17, 2025 at 4:41 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> On 11/17/25 13:12, Ron Johnson wrote:
> > On Mon, Nov 17, 2025 at 3:50 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at
> > <mailto:laurenz(dot)albe(at)cybertec(dot)at>> wrote:
> >
> > On Mon, 2025-11-17 at 18:25 +0100, Marc Millas wrote:
> > > Can someone point me to any doc describing why and how much space
> > postgres uses on the swap of a debian machine ?
> > > it's an old postgres 10, because it is used by a product for
> > which only this version is certified.
> > > (no comment on that, please)
> >
> > I'm biting down a comment.
> >
> >
> > "If it ain't broke, don't fix it" works just fine (until it doesn't).
>
> The problem is when it doesn't work anymore, the work load to move to a
> newer version is that much greater.

That's my point. If it just *kept* working, there would be no problem.

> Keeping the version within spitting
> distance of the latest supported version, to me, is a good idea.
>

As much as people love to complain about how useless PCI DSS is (see
the recent thread on TDE), there's one benefit: ensuring that companies
keep computers patched and running supported software.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2025-11-18 03:07:30 Re: postgres in swap space
Previous Message Adrian Klaver 2025-11-17 22:59:34 Re: failure to drop table due to pg_temp_7 schema