Re: tuple concurrently updated

From: 066ce286(at)free(dot)fr
To: wambacher(at)posteo(dot)de
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: tuple concurrently updated
Date: 2018-08-28 13:46:02
Message-ID: 1495817175.367327613.1535463961983.JavaMail.root@zimbra82-e14.priv.proxad.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

AAMOF, what are your fsync/wal_sync_method parameters, and what is your storage hardware ?

----- Mail original -----
De: wambacher(at)posteo(dot)de
À: pgsql-admin(at)lists(dot)postgresql(dot)org
Envoyé: Mardi 28 Août 2018 15:38:37
Objet: Re: tuple concurrently updated

so do i :( but i will try it.

in parall the preperations for a full import are running. e.g the
download will need 2 hours.

walter

Am 28.08.2018 um 15:34 schrieb 066ce286(at)free(dot)fr:
> I don't think a vacuum can handle what a pg_dump can't. But I'm maybe wrong.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alvaro Herrera 2018-08-28 13:51:34 Re: tuple concurrently updated
Previous Message pavan95 2018-08-28 13:45:42 Re: tuple concurrently updated