Re: Re: PG_UPGRADE issues "this utility can only upgrade to postgresql version 9.2."

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 13-06-19 10:16 AM, jmfox180 wrote:
so i tried to do a 

/usr/local/pgsql.old/bin/postgres -D /usr/local/pgsql.old/data start

LOG:  database system was shut down at 2013-06-19 08:10:51 CST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started

it got stuck there ^^

the i tried to 
/usr/local/pgsql.old/bin/psql -p 5432

and it turns that 
psql: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

so basically i just moved the whole pgsql8.3.2 that i had to a new folder
which is pgsql.old with sudo mv etc,etc
but i can not turn on the 8.3 server, i did try to start the new one (9.2.4)
and yes i can.

any idea?



--
View this message in context: http://postgresql.1045698.n5.nabble.com/PG-UPGRADE-issues-this-utility-can-only-upgrade-to-postgresql-version-9-2-tp5759509p5759873.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.



Does the file /var/run/postgresql/.s.PGSQL.5432.lock exist on the system you're trying to upgrade ?   If so, what's inside (cat it), does it point to your /usr/local/pgsql.old/data directory?  I've found that in my (limited) experience with pg_upgrade, it's good to run the upgrade from /tmp directory, that way the lock file gets created there and usually there's no write permission problems in /tmp either :)

Ziggy


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux