| From: | Ulf Lohbrügge <ulf(dot)lohbruegge(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Slow execution of SET ROLE, SET search_path and RESET ROLE |
| Date: | 2017-11-08 09:31:42 |
| Message-ID: | CABZYQRJHhYEGXP6W19GoXajC6Ne3N+eUsn3sn_iC3a91xC=QvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2017-11-08 0:45 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> =?UTF-8?Q?Ulf_Lohbr=C3=BCgge?= <ulf(dot)lohbruegge(at)gmail(dot)com> writes:
> > I just ran "check_postgres.pl --action=bloat" and got the following
> output:
> > ...
> > Looks fine, doesn't it?
>
> A possible explanation is that something is taking an exclusive lock
> on some system catalog and holding it for a second or two. If so,
> turning on log_lock_waits might provide some useful info.
>
> regards, tom lane
>
I just checked my configuration and found out that "log_lock_waits" was
already enabled.
Unfortunately there is no log output of locks when those long running "SET
ROLE" statements occur.
Regards,
Ulf
| From | Date | Subject | |
|---|---|---|---|
| Next Message | p kirti | 2017-11-10 10:58:41 | DB slowness after upgrade from Postgres 9.1 to 9.4 |
| Previous Message | Tom Lane | 2017-11-07 23:45:47 | Re: Slow execution of SET ROLE, SET search_path and RESET ROLE |