Re: Bug#55928: PostreSQL upgrade problem (fwd)
In article <cistron.200001250906.JAA05054@linda.lfix.co.uk>,
Oliver Elphick <email@example.com> wrote:
>Can anyone suggest where this problem may be occurring? shell-init is not
>a component of any package I have installed.
shell-init: blablabla is a warning from bash.
>shell-init: could not get current directory:
This means that someone deleted the current working directory that
that particular shell was in, and it's getcwd() function got confused
>cd_links: could not get current directory: getcwd: cannot access parent
>directories: Permission denied
That's bash complaining again about the same issue. When deleting
a directory tree, it's usually a good idea to ensure that you are
not inside it.
BTW, did you solve bug #53086 yet? The title is misleading, it's now
"PostgreSQL 6.4 -> 6.5.3 migration instructions wrong" but actually
it should be "critical: lost all databases when upgrading". And
I think it should be a release-critical bug.
It happened to me and it scared the s**t out of me. All databases
gone.. the default database location changed from /var/postgres to
/var/lib/postgres, but the 6.5.3 package doesn't move the old databases
to the new location when upgrading
I think the best thing to do is to check if /var/postgres (if not a
symlink!) and /var/lib/postgres are on the same file system. If so, rmdir
/var/lib/postgres, move /var/postgres to /var/lib/postgres and
leave a symlink behind in /var/postgres to the new location.
If not, create a /var/lib/postgres symlink pointing to the old location.
The From: and Reply-To: addresses are internal news2mail gateway addresses.
Reply to the list or to firstname.lastname@example.org (Miquel van Smoorenburg)