RE: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.

From: Mohammed Siddiqui <msiddiqui(at)net32(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Cc: Ken Sollars <Ken(at)net32(dot)com>, Matt Elliott <melliott(at)net32(dot)com>
Subject: RE: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
Date: 2024-07-25 03:51:38
Message-ID: PH0PR22MB3810937B7CD6C68022845D36B8AB2@PH0PR22MB3810.namprd22.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Configuration file is attached.

-----Original Message-----
From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Sent: Tuesday, July 23, 2024 4:33 AM
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: Mohammed Siddiqui <msiddiqui(at)net32(dot)com>; Ken Sollars <Ken(at)net32(dot)com>; Matt Elliott <melliott(at)net32(dot)com>
Subject: Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.

Hi,

> We have been seeing intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of free RAM. We have a 100 GB database with 256 GB RAM on the server so there is no shortage of RAM nor shortage in PostgreSQL buffer cache. Our swappiness setting is set to “1”.
> [...]

Please provide your postgresql.conf.

Also, why do you need a swap on such a setup? I seriously doubt that it serves any purpose.

--
Best regards,
Aleksander Alekseev

Attachment Content-Type Size
postgresql.conf application/octet-stream 30.0 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2024-07-25 06:08:49 Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607
Previous Message Masahiko Sawada 2024-07-24 21:51:20 Re: "unexpected duplicate for tablespace" problem in logical replication