Hi Adrian,
thank you again for your continued patience.
On 10 March 2016 00:20:13 +01:00, Adrian Klaver
wrote:
> On 03/09/2016 10:41 AM, wrote:
>
> > Hi Adrian,
> >
> > thank you very much for your patience. I apologise for the missing
> >
On 03/09/2016 10:41 AM, fred...@huitfeldt.com wrote:
Hi Adrian,
thank you very much for your patience. I apologise for the missing
information.
On 9 March 2016 16:13:00 +01:00, Adrian Klaver
wrote:
On 03/09/2016 04:56 AM, fred...@huitfeldt.com
Hi Adrian,
thank you very much for your patience. I apologise for the missing information.
On 9 March 2016 16:13:00 +01:00, Adrian Klaver
wrote:
> On 03/09/2016 04:56 AM, wrote:
>
> > Hi Adrian,
> >
> > thank you very much for your
On 03/09/2016 04:56 AM, fred...@huitfeldt.com wrote:
Hi Adrian,
thank you very much for your response.
I ran the "VACUUM ANALYZE" command on the master node.
Regarding log messages.
Here is the contents of the log (excluding connections/disconnections):
Assuming the below is from the
Hi Adrian,
thank you very much for your response.
I ran the "VACUUM ANALYZE" command on the master node.
Regarding log messages.
Here is the contents of the log (excluding connections/disconnections):
2016-02-22 02:30:08 GMT 24616 LOG: recovery has paused
2016-02-22 02:30:08 GMT 24616 HINT:
On 03/06/2016 10:18 PM, fred...@huitfeldt.com wrote:
HI All,
i would really appreciate any help I can get on this issue.
basically, a pg_basebackup + streaming attach, led to a database that we
could not read from afterwards.
From original post:
HI All,
i would really appreciate any help I can get on this issue.
basically, a pg_basebackup + streaming attach, led to a database that we could
not read from afterwards.
Beset regards,
Fredrik
PS please advise if this is better posted on another list.