tag 340166 moreinfo thanks Hi Markus!
Markus Schaber [2005-11-21 14:40 +0100]: > In the earlier postgresql instalations, one could define environment > variables in postgresql.env or postmaster.conf which then were exported > to the postmaster, and we could use it as LOCATION when creating new > databases in other locations. These files are obsolete and ignored in the new infrastructure. The current way to move the data directory around is to just do it and correct the /etc/postgresql/7.4/main/pgdata symlink. > dropdb: database removal failed: ERROR: postmaster environment variable > "PGDATAEXTERN" not found > > Not only that the environment variable setting was not migrated, I also > did not find the right place to reinstantiate this setting. I see, so you defined PGDATAEXTERN in postgresql.env? What does this variable do? It is not documented anywhere and not present in the default postgresql.env or postmaster.conf files. I need further information about what you want to do to be able to do something about this bug. > So I'm stuck with either dropping the whole cluster (and thus having to > migrate about 50 gig into a new cluster without stopping production > environment), or having an empty zombie-database lingering around which > confuses users. I don't understand; if you have a proper data directory somewhere, you can always integrate it in the Debian infrastructure with pg_createcluster -d /path/to/data/directory. Can you please elaborate about what the problem is? Thank you, and 'guten Rutsch'! Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Windows and Gates?
signature.asc
Description: Digital signature
