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

Huge size of memory allocation and 3000 max_connection may caused swap
space issue.

2024년 7월 25일 (목) 오후 5:01, Mohammed Siddiqui <msiddiqui(at)net32(dot)com>님이 작성:

> 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
>