| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgres stucks in deadlock detection |
| Date: | 2018-04-04 18:58:24 |
| Message-ID: | 20180404185824.53vz6er5eqb24gau@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-04-04 21:55:10 +0300, Teodor Sigaev wrote:
> > > > Have you ever observed that in the field? This sounds more artificial
> > > > than real to me.
> > >
> > > Zabbix storage with 50Gb WAL per hour on insertion.
> >
> > That's not a very detailed description. Isn't that a largely insertion
> > only workload?
>
> It's mostly insert load, collecting monitoring information. Also there are
> some read-only transactions, ~10 per second.
How are you running into deadlock detector issues then? Where do the
significant number of heavyweight lock weights come from?
> We didn't invent this from mind, client came to us with support request, now
> we have two different cases.
You gotta actually start describing those then.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-04-04 19:09:55 | Re: pgsql: New files for MERGE |
| Previous Message | Pavan Deolasee | 2018-04-04 18:55:27 | Re: pgsql: New files for MERGE |