From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | basti <basti(at)unix-solution(dot)de> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: WAL replication wrong collate |
Date: | 2017-08-16 05:05:09 |
Message-ID: | CAB7nPqRsgvss3pqhEpRxQeoPw-4rk1KmVUK9QNVvL71VJEGphg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 15, 2017 at 4:45 AM, basti <basti(at)unix-solution(dot)de> wrote:
> i have fixed. pg_update has create a wrong cluster
Let's be sure that we are not talking about a bug here, because you
are giving no details so it is hard to know if what you are seeing is
caused by an incorrect operation, or if that's an actual bug. So,
could you answer the following questions?
1) Are you referring to pg_upgrade instead of pg_update?
2) How did you do the upgrade of the standby server?
3) What are the original version of the server and the new version?
4) What is the exact order of the operations you did that made the
state you saw happen?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Samad | 2017-08-16 05:32:26 | Begginers question |
Previous Message | Jeff Janes | 2017-08-15 22:26:26 | Re: How to delete default privileges |