Hi Justin
Thanks for your update.
Postgres is just an OS Process, so should be monitored like any other.
What OS are you using ?
> I am using Centos 7.5.
Know that the OS may attribute "shared buffers" to different processes, or
multiple processes.
It's almost always a bad idea to kill
Hi Justin
I list the server configuration for your reference.
postgres=# SELECT name, current_setting(name), source
postgres-# FROM pg_settings
postgres-# WHERE source NOT IN ('default', 'override');
name | current_setting |
source
---
> enable_seqscan = 'off'
Why is this here ? I think when people set this, it's because they "want to
use more index scans to make things faster". But index scans aren't
necessarily faster, and this tries to force their use even when it will be
slower. It's better to address the queries that are
Hi Justin
Thanks for you explaination.
> > What postgres version ?
> > How was it installed ? From souce? From a package ?
I am using Postgres 11.1 .It's installed by package.
Check:
ps -fu postgres
# then:
sudo cat /proc/2948/limits
root@bl4n3icpms ~]# sudo cat /proc/21731/limits
Lim
On Fri, May 27, 2022 at 01:39:15AM +0800, 徐志宇徐 wrote:
> Hi Justin
>
> Thanks for you explaination.
>
> > > What postgres version ?
> > > How was it installed ? From souce? From a package ?
> I am using Postgres 11.1 .It's installed by package.
This is quite old, and missing ~4 years of
