Re: Re: database system identifier differs between the primary and standby

Finally I setup two machines for primary and backup using the following link.
http://wiki.postgresql.org/wiki/Streaming_Replication

But after starting the backup I got the following messages and postgresql service doesn't start.

2011-04-22 14:37:54 ETC/GMT LOG: database system was shut down in recovery at 2011-04-22 14:23:02 ETC/GMT
2011-04-22 14:37:54 ETC/GMT DEBUG: restore_command = 'cp /opt/PostgreSQL/9.0/data/archive/%f "%p"'
2011-04-22 14:37:54 ETC/GMT DEBUG: standby_mode = 'on'
2011-04-22 14:37:54 ETC/GMT DEBUG: primary_conninfo = 'host=10.20.9.181 port=5432 user=postgres password=Password1'
2011-04-22 14:37:54 ETC/GMT DEBUG: trigger_file = '/tmp/trigger'
2011-04-22 14:37:54 ETC/GMT LOG: entering standby mode
2011-04-22 14:37:54 ETC/GMT DEBUG: executing restore command "cp /opt/PostgreSQL/9.0/data/archive/000000010000000000000007 "pg_xlog/RECOVERYXLOG""
2011-04-22 14:37:54 ETC/GMT LOG: restored log file "000000010000000000000007" from archive
2011-04-22 14:37:54 ETC/GMT DEBUG: got WAL segment from archive
2011-04-22 14:37:54 ETC/GMT LOG: record with zero length at 0/700011C
2011-04-22 14:37:54 ETC/GMT LOG: record with zero length at 0/700011C
2011-04-22 14:37:54 ETC/GMT DEBUG: find_in_dynamic_libpath: trying "/opt/PostgreSQL/9.0/lib/postgresql/libpqwalreceiver"
2011-04-22 14:37:54 ETC/GMT DEBUG: find_in_dynamic_libpath: trying "/opt/PostgreSQL/9.0/lib/postgresql/libpqwalreceiver.so"
2011-04-22 14:37:55 ETC/GMT FATAL: the database system is starting up
2011-04-22 14:37:55 ETC/GMT DEBUG: shmem_exit(1): 0 callbacks to make
2011-04-22 14:37:55 ETC/GMT DEBUG: proc_exit(1): 1 callbacks to make
2011-04-22 14:37:55 ETC/GMT DEBUG: exit(1)
2011-04-22 14:37:55 ETC/GMT DEBUG: shmem_exit(-1): 0 callbacks to make
2011-04-22 14:37:55 ETC/GMT DEBUG: proc_exit(-1): 0 callbacks to make
2011-04-22 14:37:55 ETC/GMT DEBUG: forked new backend, pid=1256 socket=8
2011-04-22 14:37:55 ETC/GMT DEBUG: reaping dead processes
2011-04-22 14:37:55 ETC/GMT DEBUG: server process (PID 1256) exited with exit code 1

Please help me with this.

Regards,

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(dot)deka(at)siemens(dot)com

-----Original Message-----
From: Deka, Rajib IN MAA SL
Sent: Friday, April 22, 2011 12:26 PM
To: 'Cédric Villemain'; Robert Haas
Cc: Simon Riggs; pgsql-hackers
Subject: RE: [HACKERS] Re: database system identifier differs between the primary and standby

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(dot)deka(at)siemens(dot)com

-----Original Message-----
From: Cédric Villemain [mailto:cedric(dot)villemain(dot)debian(at)gmail(dot)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(at)gmail(dot)com>:
> On Thu, Apr 21, 2011 at 6:38 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On Thu, Apr 21, 2011 at 10:31 AM, rajibdk <rajib(dot)deka(at)siemens(dot)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 produced them.
*/
)

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(at)postgresql(dot)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 received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system.
Thank You.