Thanks a lot.
I got the idea now.
Rajib Deka
SIEMENS Ltd.
Robert V Chandran Tower, First Floor, West Wing,
#149, Velechery Tambaram Main Road, Pallikaranai, Chennai-100, INDIA.
www.siemens.com
Mob: +91-9176780669 | E-Mail: rajib.deka@siemens.com
-----Original Message-----
From: Cédric Villemain [mailto:cedric.villemain.debian@gmail.com]
Sent: Thursday, April 21, 2011 9:56 PM
To: Robert Haas
Cc: Simon Riggs; Deka, Rajib IN MAA SL; pgsql-hackers
Subject: Re: [HACKERS] Re: database system identifier differs between the primary and standby
2011/4/21 Robert Haas <robertmhaas@gmail.com>:
> On Thu, Apr 21, 2011 at 6:38 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> On Thu, Apr 21, 2011 at 10:31 AM, rajibdk <rajib.deka@siemens.com> wrote:
>>> What does that database system identifier means? Is it related to DB
>>> transactions' or unique to a version?
>>
>> Regrettably, it means you didn't follow the documented procedure.
>>
>> It isn't possible to do it any other way, so those questions are a distraction.
>
> I think they are perfectly good questions. If someone is trying to
> understand how our product works, we should encourage that.
Agree those are perfectly good question to ask on -general. (but on
hackers it looks excessive)
Rajib: this is relative to initdb, it produces one key to be able to
check later if postgresql is restoring the good files.
(
from sources : /* * Unique system identifier --- to ensure we match up xlog files with the * installation that
producedthem. */
)
Robert, Please don't add confusion to your signature : PostgreSQL is a
community project not an enterprise product.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support
Important notice: This e-mail and any attachment there to contains corporate proprietary information. If you have
receivedit by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from
yoursystem.
Thank You.
