| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Gould <daveg(at)sonic(dot)net>, 石勇虎 <SHIYONGHU651(at)pingan(dot)com(dot)cn>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: response time is very long in PG9.5.5 using psql or jdbc |
| Date: | 2018-02-13 22:21:02 |
| Message-ID: | 20180213222102.ku2o3oy3tvasn3hx@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2018-02-13 17:06:36 -0500, Tom Lane wrote:
> Now, those issues seemed to be associated with needing to rebuild the
> relcache init file, so you wouldn't expect them to repeat on every
> connection ... but maybe the OP has something going on that causes the
> init file to get invalidated constantly. That'd have to be on top of
> some other massive performance problem, but at least you could see how
> catalog bloat could possibly lead to this type of symptom, seeing that
> init file rebuild requires some catalog seqscans.
One of the OP's examples shows the connection establishment separate
from the slowdown however. Shouldn't that preclude relcache init file
rebuilds being involved?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-13 22:37:09 | Re: response time is very long in PG9.5.5 using psql or jdbc |
| Previous Message | Tom Lane | 2018-02-13 22:06:36 | Re: response time is very long in PG9.5.5 using psql or jdbc |