Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dSk6N-0008SI-Po for pgsql-performance@arkaria.postgresql.org; Wed, 05 Jul 2017 13:12:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dSk6N-0005RI-CP for pgsql-performance@arkaria.postgresql.org; Wed, 05 Jul 2017 13:12:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dSk4Y-0003Rg-1r for pgsql-performance@postgresql.org; Wed, 05 Jul 2017 13:10:26 +0000 Received: from mail-qt0-x233.google.com ([2607:f8b0:400d:c0d::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dSk4U-0000F4-2e for pgsql-performance@postgresql.org; Wed, 05 Jul 2017 13:10:25 +0000 Received: by mail-qt0-x233.google.com with SMTP id 32so185611857qtv.1 for ; Wed, 05 Jul 2017 06:10:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AmzuRO8koiGNzVaV0fvDq64L4Lp7H5ddhK+StGJ4jYI=; b=vP7g7d/edRqD9V9zFgI8ZBeskH7nKl+Adi5lyyPiq8sW+FWN3qzmavThlBRNPt2vjM /1gXZ8EgrcPOGfJpzlZvXExTkJs0oGY7PgEouSBMaKsHx3NTX7DqoYNHVj10qO5HRZmY SCX7cUar0LhulKA1ZVH6C6YAHb2aIhTBg6xYWJjRNlF4ukcwu7KD5+Vs/xU8H7tkxXCZ 73aKOVt/+wDsB3nMgQ2EgndTrhkRKn4FjR9TlL+6PQTgHULpaSO48hoT8442nya9fkA5 Y90DEP6Eu40GW/giCYoGW5pyQNsg32l2hxTAbAWEcB77doLDE7txGXpu40NoyIOgJC4A 3/ZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AmzuRO8koiGNzVaV0fvDq64L4Lp7H5ddhK+StGJ4jYI=; b=TLotSOB168DDp4SLohuXGeJ83aZAJ3VDWc8YMJR3eAHXUm9RDpyJ+VvXDAFSXcnDyz /p96V1nxK9ndPOyXO6GqN3v7U3TcJGwA/a/AScOWbH2oWBbOC2A5KyiuCMotRkPkLsNf +OAcERtslKZz9nz6d2G/2+/q2XhBY0ry0r6+HZlc/oP+brTH1BKor1WpWxSBNj7QGWsN v0ptcqoY1hO6LPybsj9Ci+O+9DENZ7dde2olEbHBcYVfukhfWEeRnoJSNMMEBBwhoyuk gGTw6SGELod7qRsWM4Wu0DZYa7kpzBl82fgywJGR4gMt5Ax9TK3Lg0Kcien3NghA9voC RmfA== X-Gm-Message-State: AIVw112208SgezSk62NbbGNtSmLNx9mSYbp+yjm2VmNqvZXk1yOx4CRP H4/sYhnQPYlIfGJzSbx0nQLRcNFu5w== X-Received: by 10.237.58.167 with SMTP id o36mr18516150qte.128.1499260220487; Wed, 05 Jul 2017 06:10:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.97.100 with HTTP; Wed, 5 Jul 2017 06:10:19 -0700 (PDT) In-Reply-To: References: From: Scott Marlowe Date: Wed, 5 Jul 2017 07:10:19 -0600 Message-ID: Subject: Re: Unable to start the slave instance To: Daulat Ram Cc: "pgsql-performance@postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Wed, Jul 5, 2017 at 3:26 AM, Daulat Ram wrote: > Hi experts, > > We have configured a replication environment in Windows 10. But I am getting > below the error messages while starting slave instance. > > > > Error: > > > > 2017-07-05 00:00:02 IST LOG: restored log file "000000010000000000000022" > from archive > > 2017-07-05 00:00:02 IST LOG: WAL file is from different database system: > WAL file database system identifier is 6438799484563175092, pg_control > database system identifier is 6379088242155134709. > > 2017-07-05 00:00:02 IST FATAL: database system identifier differs between > the primary and standby > > 2017-07-05 00:00:02 IST DETAIL: The primary's identifier is > 6438799484563175092, the standby's identifier is 6379088242155134709. > So how did you get to here? It doesn't look like a proper rsync or pg_basebackup method got you here. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance