| From: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: WIP Patch: Pgbench Serialization and deadlock errors |
| Date: | 2017-07-14 15:01:56 |
| Message-ID: | 5c9f781b61d2292fcbe16ab4ff51499a@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Well, the short version may be to only do a full transaction retry and
> to document that for now savepoints are not handled, and to let that
> for future work if need arises.
I agree with you.
> For progress the output must be short and readable, and probably we do
> not care about whether retries came from this or that, so I would let
> that out.
>
> For log and aggregated log possibly that would make more sense, but it
> must stay easy to parse.
Ok!
--
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrien Nayrat | 2017-07-14 15:20:32 | Re: PG 10 release notes |
| Previous Message | Marina Polyakova | 2017-07-14 14:54:37 | Re: WIP Patch: Pgbench Serialization and deadlock errors |