public inbox for [email protected]
help / color / mirror / Atom feedRe: postgres in swap space
2+ messages / 2 participants
[nested] [flat]
* Re: postgres in swap space
@ 2025-11-17 21:41 Adrian Klaver <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Adrian Klaver @ 2025-11-17 21:41 UTC (permalink / raw)
To: Ron Johnson <[email protected]>; [email protected] <[email protected]>
On 11/17/25 13:12, Ron Johnson wrote:
> On Mon, Nov 17, 2025 at 3:50 PM Laurenz Albe <[email protected]
> <mailto:[email protected]>> 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. Keeping the version within spitting
distance of the latest supported version, to me, is a good idea.
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
--
Adrian Klaver
[email protected]
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: postgres in swap space
@ 2025-11-18 00:18 Ron Johnson <[email protected]>
parent: Adrian Klaver <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Ron Johnson @ 2025-11-18 00:18 UTC (permalink / raw)
To: [email protected] <[email protected]>
On Mon, Nov 17, 2025 at 4:41 PM Adrian Klaver <[email protected]>
wrote:
> On 11/17/25 13:12, Ron Johnson wrote:
> > On Mon, Nov 17, 2025 at 3:50 PM Laurenz Albe <[email protected]
> > <mailto:[email protected]>> 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!
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-11-18 00:18 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-11-17 21:41 Re: postgres in swap space Adrian Klaver <[email protected]>
2025-11-18 00:18 ` Ron Johnson <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox