2018-05-24 8:30 GMT+02:00 Andrey Borodin :
> Hi!
>
> > 24 мая 2018 г., в 0:55, Paolo Crosato
> написал(а):
> >
> > 1) VACUUM FULL was issued after the first time the error occurred, and a
> couple of times later. CLUSTER was never run.
> > 2) Several fail
2018-05-23 20:32 GMT+02:00 Andres Freund :
> On 2018-05-22 16:39:58 -0700, Andres Freund wrote:
> > Hi,
> >
> > On 2018-05-23 00:04:26 +0200, Paolo Crosato wrote:
> > > I managed to recover the log of the first time we run into the issue,
> the
> >
2018-05-23 1:39 GMT+02:00 Andres Freund :
> Hi,
>
> On 2018-05-23 00:04:26 +0200, Paolo Crosato wrote:
> > I managed to recover the log of the first time we run into the issue, the
> > error was the same but on template1:
> >
> > May 8 11:26:46 xxx postgres[
Good evening,
2018-05-22 23:19 GMT+02:00 Andres Freund :
> Hi,
>
> On 2018-05-22 21:43:01 +0200, Paolo Crosato wrote:
> > > Could you report the result of
> > > select ctid, xmin, xmax from pg_authid ;
> > >
> >
> > This is the result:
> >
Hello,
2018-05-22 18:49 GMT+02:00 Andres Freund :
> Hi,
>
> On 2018-05-22 16:18:20 +0200, Paolo Crosato wrote:
> > PostgreSQL version number you are running:
> >
> > PostgreSQL 10.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5
> > 20150623 (Red Hat
lert was given at all since the cluster has been
running.
Thank you in advance for any answer.
Paolo Crosato
