Thread: pg_upgrade from V9.3.3 to V9.4.0

Hi all,

While we're not planning to migrate to the new version, I'm trying to gain some experience as the streaming replication
hasreally changed in this version and indicates future  
directions for it. My environment is virtualized CentO/S 6.5, and this particular server is the current primary, not a
standby.My problem is that the pg_upgrade is just hanging -  
for over an hour, before I killed it. I only see a "Verifying Cluster" message, and that's it. Even the 3 logs written
bypg_upgrade, don't really tell me any more. Am I trying to  
go too far with this upgrade? Do I need to bring it V9.3.4 first, or what? The behavior just seems a bit odd. I've only
runthis prior going from 9.2.2 to 9.3.3 and that had no issues. 
--
Jay

On Fri, Jan  9, 2015 at 05:27:15PM -0500, John Scalia wrote:
> Hi all,
>
> While we're not planning to migrate to the new version, I'm trying
> to gain some experience as the streaming replication has really
> changed in this version and indicates future directions for it. My
> environment is virtualized CentO/S 6.5, and this particular server
> is the current primary, not a standby. My problem is that the
> pg_upgrade is just hanging - for over an hour, before I killed it. I
> only see a "Verifying Cluster" message, and that's it. Even the 3
> logs written by pg_upgrade, don't really tell me any more. Am I
> trying to go too far with this upgrade? Do I need to bring it V9.3.4
> first, or what? The behavior just seems a bit odd. I've only run
> this prior going from 9.2.2 to 9.3.3 and that had no issues.

I have never heard of a hang like that.  I would try V9.3.4.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

Thanks Bruce,

I'll give that a try on Monday morning.
--
Jay

On 1/9/2015 5:39 PM, Bruce Momjian wrote:
> On Fri, Jan  9, 2015 at 05:27:15PM -0500, John Scalia wrote:
>> Hi all,
>>
>> While we're not planning to migrate to the new version, I'm trying
>> to gain some experience as the streaming replication has really
>> changed in this version and indicates future directions for it. My
>> environment is virtualized CentO/S 6.5, and this particular server
>> is the current primary, not a standby. My problem is that the
>> pg_upgrade is just hanging - for over an hour, before I killed it. I
>> only see a "Verifying Cluster" message, and that's it. Even the 3
>> logs written by pg_upgrade, don't really tell me any more. Am I
>> trying to go too far with this upgrade? Do I need to bring it V9.3.4
>> first, or what? The behavior just seems a bit odd. I've only run
>> this prior going from 9.2.2 to 9.3.3 and that had no issues.
> I have never heard of a hang like that.  I would try V9.3.4.
>

On Fri, Jan  9, 2015 at 05:42:34PM -0500, John Scalia wrote:
> Thanks Bruce,
>
> I'll give that a try on Monday morning.

Might was well go to 9.3.5 for testing.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

On Sat, Jan 10, 2015 at 3:57 AM, John Scalia <jayknowsunix@gmail.com> wrote:

Hi all,

While we're not planning to migrate to the new version, I'm trying to gain some experience as the streaming replication has really changed in this version and indicates future directions for it. My environment is virtualized CentO/S 6.5, and this particular server is the current primary, not a standby. My problem is that the pg_upgrade is just hanging - for over an hour, before I killed it. I only see a "Verifying Cluster" message, and that's it. Even the 3 logs written by pg_upgrade, don't really tell me any more. Am I trying to go too far with this upgrade? Do I need to bring it V9.3.4 first, or what? The behavior just seems a bit odd. I've only run this prior going from 9.2.2 to 9.3.3 and that had no issues.
--
Jay



--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Hi John Scalia,

I have tried pg_upgrade from 9.3.3 to 9.4.0 and i have done with the following procedure which will solve your problem.

Create .pgpass file in users home directory ~/.pgpass and add both server with their respective user & password

Now Shut down 9.3.3 & 9.4.0 cluster

Now when ever you run pg_upgrade utility the present working directory (pwd) should have write access of the current user e.g postgres

First just check if clusters are Clusters are compatible with using -c options

Example:

/opt/PostgreSQL/9.4/bin/pg_upgrade -c -v -d /tmp/PostgreSQL/9.3.3/data/ -D /tmp/PostgreSQL/9.4.0/data/ -b /opt/PostgreSQL/9.3.3/bin/ -B /opt/PostgreSQL/9.4/bin/ -p 5888 -P 5999 -U postgres

If Result says Clusters are compatible then remove -c and start upgrading

Example:

/opt/PostgreSQL/9.4/bin/pg_upgrade -v -d /tmp/PostgreSQL/9.3.3/data/ -D /tmp/PostgreSQL/9.4.0/data/ -b /opt/PostgreSQL/9.3.3/bin/ -B /opt/PostgreSQL/9.4/bin/ -p 5888 -P 5999 -U postgres

If Result says Upgrade Complete then your upgrade is completed successfully.

I am also attaching the one file for reference.

Hope this will resolve your problem.

--
Thanks & Regards,
Harshad Adalkonda
Database Administrator

http://www.shreeyansh.com

On Sat, Jan 10, 2015 at 07:13:00PM +0530, Harshad Adalkonda wrote:
>
> On Sat, Jan 10, 2015 at 3:57 AM, John Scalia <jayknowsunix@gmail.com> wrote:
>
>     Hi all,
>
>     While we're not planning to migrate to the new version, I'm trying to gain
>     some experience as the streaming replication has really changed in this
>     version and indicates future directions for it. My environment is
>     virtualized CentO/S 6.5, and this particular server is the current primary,
>     not a standby. My problem is that the pg_upgrade is just hanging - for over
>     an hour, before I killed it. I only see a "Verifying Cluster" message, and
>     that's it. Even the 3 logs written by pg_upgrade, don't really tell me any
>     more. Am I trying to go too far with this upgrade? Do I need to bring it
>     V9.3.4 first, or what? The behavior just seems a bit odd. I've only run
>     this prior going from 9.2.2 to 9.3.3 and that had no issues.
>
> Hi John Scalia,
>
> I have tried pg_upgrade from 9.3.3 to 9.4.0 and i have done with the following
> procedure which will solve your problem.
>
> Create .pgpass file in users home directory ~/.pgpass and add both server with
> their respective user & password

Oh, so you are thinking it is waiting for a password?  Wouldn't it say
"Password:"?

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

On 1/10/2015 3:32 PM, Bruce Momjian wrote:
> On Sat, Jan 10, 2015 at 07:13:00PM +0530, Harshad Adalkonda wrote:
>> On Sat, Jan 10, 2015 at 3:57 AM, John Scalia <jayknowsunix@gmail.com> wrote:
>>
>>      Hi all,
>>
>>      While we're not planning to migrate to the new version, I'm trying to gain
>>      some experience as the streaming replication has really changed in this
>>      version and indicates future directions for it. My environment is
>>      virtualized CentO/S 6.5, and this particular server is the current primary,
>>      not a standby. My problem is that the pg_upgrade is just hanging - for over
>>      an hour, before I killed it. I only see a "Verifying Cluster" message, and
>>      that's it. Even the 3 logs written by pg_upgrade, don't really tell me any
>>      more. Am I trying to go too far with this upgrade? Do I need to bring it
>>      V9.3.4 first, or what? The behavior just seems a bit odd. I've only run
>>      this prior going from 9.2.2 to 9.3.3 and that had no issues.
>>
>> Hi John Scalia,
>>
>> I have tried pg_upgrade from 9.3.3 to 9.4.0 and i have done with the following
>> procedure which will solve your problem.
>>
>> Create .pgpass file in users home directory ~/.pgpass and add both server with
>> their respective user & password
> Oh, so you are thinking it is waiting for a password?  Wouldn't it say
> "Password:"?
>
I saw nothing on the terminal, nor anything in the logfiles indicating a password request.