Skip site navigation (1) Skip section navigation (2)

BUG #6347: Reopening bug #6085

From: alexander(dot)fortin(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6347: Reopening bug #6085
Date: 2011-12-19 15:06:31
Message-ID: E1RcenP-00009B-FY@wrigleys.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged on the website:

Bug reference:      6347
Logged by:          Alexander Fortin
Email address:      alexander(dot)fortin(at)gmail(dot)com
PostgreSQL version: 9.1.2
Operating system:   Ubuntu 10.04.3
Description:        

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 = '/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"?


Responses

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2011-12-19 15:09:11
Subject: Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb]
Previous:From: Robert HaasDate: 2011-12-19 14:31:56
Subject: Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb]

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group