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

Re: BUG #6347: Reopening bug #6085

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: alexander(dot)fortin(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6347: Reopening bug #6085
Date: 2012-02-03 14:59:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Mon, Dec 19, 2011 at 03:06:31PM +0000, alexander(dot)fortin(at)gmail(dot)com wrote:
> 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"?

Yes.  I wasn't clear in my email reply:

When I said this will be fixed in 9.1, I meant pg_ctl will work in 9.1
for non-default socket directories, but when the 9.1 pg_upgrade accesses
the 8.4 server, it has to use the 8.4 pg_ctl to do it, and that can't be
fixed in a back-branch.

I think we can only call this fixed when the old and new server is >= PG
9.1.  Yeah, this isn't good, but it is the best we can do.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + It's impossible for everything to be true. +

In response to


pgsql-bugs by date

Next:From: Duncan RanceDate: 2012-02-03 15:24:50
Subject: Re: BUG #6425: Bus error in slot_deform_tuple
Previous:From: Heikki LinnakangasDate: 2012-02-03 12:58:56
Subject: Re: BUG #6430: Wal Segment Size is 128GB

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