From: Pepe TD Vo <pepevo@yahoo.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
To: Alvaro Aguayo <aaguayo@opensysperu.com>
Subject: Re: database lagging
Date: Fri, 23 Jul 2021 18:27:01 +0000 (UTC)
Message-ID: <678607417.590943.1627064821704@mail.yahoo.com> (raw)
In-Reply-To: <SC1P15201MB223815E976EE2CACECFC7572AFE59@SC1P15201MB2238.LAMP152.PROD.OUTLOOK.COM>
References: <1396983439.574027.1627062741652.ref@mail.yahoo.com>
<1396983439.574027.1627062741652@mail.yahoo.com>
<SC1P15201MB223815E976EE2CACECFC7572AFE59@SC1P15201MB2238.LAMP152.PROD.OUTLOOK.COM>
nothing is running. Only psql and background writer, checkpointermain, walwritermain, autovacuummain, logicalLauncherMain from pg_stat_activity (6 rows) nothing else is running
no row select on "select relation::regclass, * from pg_locks where not granted;
select on "select relation::regclass, * from pg_locks;
2 rows for pg_locks relation for AccessShareLock and virtualxid for ExclusiveLock.
What else can I check and correct ?
Bach-Nga
No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love, and forgive more.To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
**Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely rich *** Faithful talent *** Sharing success
On Friday, July 23, 2021, 02:07:15 PM EDT, Alvaro Aguayo <aaguayo@opensysperu.com> wrote:
<!--#yiv9051853937 _filtered {} _filtered {}#yiv9051853937 #yiv9051853937 p.yiv9051853937MsoNormal, #yiv9051853937 li.yiv9051853937MsoNormal, #yiv9051853937 div.yiv9051853937MsoNormal {margin:0cm;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv9051853937 span.yiv9051853937EmailStyle18 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv9051853937 .yiv9051853937MsoChpDefault {font-size:10.0pt;} _filtered {}#yiv9051853937 div.yiv9051853937WordSection1 {}-->
Is there any other thing running with that database? If so, I would consider a locking problem. CREATE/ALTER ROLE should never take too much time, unless there is some kind of lock in a global catalog.
Regards,
Alvaro Aguayo
Operations Manager
Open Comb Systems E.I.R.L.
From: Pepe TD Vo <pepevo@yahoo.com>
Sent: 23 July 2021 12:52
To: pgsql-admin@lists.postgresql.org
Subject: database lagging
I am doing CIS Benchmart on Postgreql 12. After alter parameters and when I tried to create a new role. It's lagging and didn't prompt out the result, until I hit the ctl C key. Even alter role. All I needed to hit ctl C key if not, it hung there for ever. Is there a way to fix it?
postgres=# create role appuser;
^CCancel request sent
CREATE ROLE
postgres=# ALTER ROLE appuser NOSUPERUSER;
^CCancel request sent
ALTER ROLE
postgres=# ALTER ROLE appuser NOREPLICATION;
^CCancel request sent
ALTER ROLE
postgres=# ALTER ROLE appuser NOCREATEROLE;
^CCancel request sent
ALTER ROLE
postgres=# ALTER ROLE appuser NOHERIT;
^CCancel request sent
ALTER ROLE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pepevo@yahoo.com, pgsql-admin@lists.postgresql.org, aaguayo@opensysperu.com
Subject: Re: database lagging
In-Reply-To: <678607417.590943.1627064821704@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox