From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Guillaume Drolet <droletguillaume(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cluster seems broken after pg_basebackup |
Date: | 2015-02-11 15:26:32 |
Message-ID: | 54DB74A8.9020608@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/10/2015 08:38 AM, Guillaume Drolet wrote:
>
> Adrian, in response to your question:
>
> 2015-02-06 07:11:38 EST FATAL: le rôle « 208375PT$ » n'existe pas
>
>
> So where is role 208375PT$ supposed to come from?
>
> I found that when I stop/start/restart pgsql through the services.msc
> application in Windows, this message is issued in the log file. This
> makes sense since the account I use to start the services.msc
> application is my admin account, 208375PT\Admlocal.
>
> If I use instead the command line with "pg_ctl restart -U postgres", I
> don't get this message in the log file.
>
Thanks for the explanation. I would say at this point the error is just
noise, but it is nice to know where it came from. Seems a corruption
issue on the master, as others have pointed out, is at the heart of the
matter.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Nestor A. Diaz | 2015-02-11 15:49:07 | The return of the auto-vacuum |
Previous Message | Gustavo Lopes | 2015-02-11 15:19:48 | EINTR causes panic (data dir on btrfs) |