116 reputation
3
bio website phrogz.net
location Boulder, CO
age 41
visits member for 2 years, 5 months
seen Aug 1 at 14:19

Feb
25
comment Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
I'm bringing the server in line with several other that are also running 9.1. The 9.0 server is on 5432, the 9.1 server is on 5433.
Feb
25
comment Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
I may have to just give up and manually pg_dump and then import each database from the old into the new. The only problem with this is that the server is low on disk space (only a few gigs on each drive) and the old data directory is just about at 3GB already; so presumably I'll be exporting several gigs of data and then creating another copy of that in the 9.1 cluster before I can delete the intermediary .sql files and the 9.0 cluster.
Feb
25
comment Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
@CraigRinger Per the guide, I'm logged into a cmd.exe using runas as the postgres admin, postgres. This same user has Full Control permissions allocated to the both the old and new data directories. In both cases the actual Owner (Properties▸Security▸Advanced▸Owner) is set to the Administrators group (which the postgres account is not a part of). Note that the 9.0 server is able to operate perfectly under this set of permissions.
Feb
25
comment Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
@CraigRinger Nothing relevant to the conversion, as far as I can tell.
Feb
24
awarded  Student
Feb
24
revised Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
added 7 characters in body
Feb
24
awarded  Editor
Feb
24
revised Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
added 6732 characters in body
Feb
24
asked Problems executing pg_ctl during pg_upgrade from 9.0 to 9.1 on Windows
Feb
23
comment pg_upgrade fails with an unspecified error
For future users finding this topic because of the "servicing old cluster" message: if you truly do not have a postmaster running, and you are certain that you shut down the postmaster cleanly, this message means that there is a postmaster.id file in your directory that you need to delete.
Feb
23
awarded  Supporter