BUG #6347: Reopening bug #6085
| От | alexander.fortin@gmail.com |
|---|---|
| Тема | BUG #6347: Reopening bug #6085 |
| Дата | |
| Msg-id | E1RcenP-00009B-FY@wrigleys.postgresql.org обсуждение исходный текст |
| Ответы |
Re: BUG #6347: Reopening bug #6085
|
| Список | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 6347
Logged by: Alexander Fortin
Email address: alexander.fortin@gmail.com
PostgreSQL version: 9.1.2
Operating system: Ubuntu 10.04.3
Description:=20=20=20=20=20=20=20=20
Hi folks. I'm testing 9.1.2 (source compiled) pg_upgrade (upgrading from
8.4.9) and it seems that the problem exposed in bug #6085 is still there. In
my case, the only way to make pg_upgrade work is to actually force
unix_socket_directory =3D '/tmp/' for the 8.4.9 cluster.
Running in verbose mode
Performing Consistency Checks on Old Live Server
------------------------------------------------
Checking current, bin, and data directories ok
Checking cluster versions ok
connection to database failed: could not connect to server: No such file or
directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
В списке pgsql-bugs по дате отправления: