| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "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-17 21:41:14 |
| Message-ID: | 97810758-0f5f-4e41-8e25-ac9dcd7a255e@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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. 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
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter 'PMc' Much | 2025-11-17 22:08:17 | Re: failure to drop table due to pg_temp_7 schema |
| Previous Message | Ron Johnson | 2025-11-17 21:12:10 | Re: postgres in swap space |