Re: [BUGS] BUG #6627: Error while launching pgAdmin III
Pooja Khobragade wrote: > I guess I get this error because there are two versions of > postgreSQL installed on the same machine. It sounds like that may be part of the problem, or an improper or incomplete attempt at an update to a new major version. On the other hand, there is definitely more to the problem than running two versions on the same machine. In our shop, we do that all the time without problems. It can work fine as long as you manage it correctly. Have you performed an upgrade to a new major version of PostgreSQL lately? Have you ever moved or copied PostgreSQL executable files from one location to another? -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6627: Error while launching pgAdmin III
Tom & Kevin, Thanks for your reply. I guess I get this error because there are two versions of postgreSQL installed on the same machine. Regards, Pooja -Original Message- From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov] Sent: Friday, May 04, 2012 7:54 PM To: Pooja Khobragade; Tom Lane Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #6627: Error while launching pgAdmin III Tom Lane wrote: > pooja_khobrag...@persistent.co.in writes: >> Error while connecting to server FATAL: shmemindex size is wrong for >> datastructure xlog ctl : expected xxx actaul xxx > > That's an interesting one. The only theory that comes to mind is that > you've got multiple versions of Postgres installed on your machine, > and when the postmaster tries to launch a subprocess, the wrong copy > of postgres.exe is being selected for some reason. Or possibly you > updated in place and didn't restart the postmaster? Just so the OP is aware, running pg_ctl with the restart option is generally not adequate to prevent problems with an update, in place or not. The postmaster must be stopped and then started. Some service scripts may do that, others don't. So the safe thing, unless you know exactly how your service script is written, is to stop and then start again. -Kevin DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6627: Error while launching pgAdmin III
Tom Lane wrote: > pooja_khobrag...@persistent.co.in writes: >> Error while connecting to server FATAL: shmemindex size is wrong >> for datastructure xlog ctl : expected xxx actaul xxx > > That's an interesting one. The only theory that comes to mind is > that you've got multiple versions of Postgres installed on your > machine, and when the postmaster tries to launch a subprocess, the > wrong copy of postgres.exe is being selected for some reason. Or > possibly you updated in place and didn't restart the postmaster? Just so the OP is aware, running pg_ctl with the restart option is generally not adequate to prevent problems with an update, in place or not. The postmaster must be stopped and then started. Some service scripts may do that, others don't. So the safe thing, unless you know exactly how your service script is written, is to stop and then start again. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6627: Error while launching pgAdmin III
pooja_khobrag...@persistent.co.in writes: > Error while connecting to server FATAL: shmemindex size is wrong for > datastructure xlog ctl : expected xxx actaul xxx That's an interesting one. The only theory that comes to mind is that you've got multiple versions of Postgres installed on your machine, and when the postmaster tries to launch a subprocess, the wrong copy of postgres.exe is being selected for some reason. Or possibly you updated in place and didn't restart the postmaster? regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
