From: 066ce286@free.fr
To: wambacher@posteo.de
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 15:46:02 +0200 (CEST)
Message-ID: <1495817175.367327613.1535463961983.JavaMail.root@zimbra82-e14.priv.proxad.net> (raw)
In-Reply-To: <84c2baff-89e3-931f-232a-f6ca832eb364@posteo.de>
AAMOF, what are your fsync/wal_sync_method parameters, and what is your storage hardware ?
----- Mail original -----
De: wambacher@posteo.de
À: pgsql-admin@lists.postgresql.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@free.fr:
> I don't think a vacuum can handle what a pg_dump can't. But I'm maybe wrong.
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: 066ce286@free.fr, wambacher@posteo.de, pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
In-Reply-To: <1495817175.367327613.1535463961983.JavaMail.root@zimbra82-e14.priv.proxad.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox