From: tushar <tushar.ahuja@enterprisedb.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: [v15 beta] pg_upgrade failed if earlier executed with -c switch
Message-ID: <77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com>
Date: Fri, 3 Jun 2022 16:49:36 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------C62F7F15D2FCDAF8EB5DD47E"
Content-Language: en-US
Archived-At: 
 <https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b%40enterprisedb.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------C62F7F15D2FCDAF8EB5DD47E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

While performing pg_upgrade from v15Beta binaries/source,
I got this error below error

could not create directory "d2/pg_upgrade_output.d": File exists
Failure, exiting


*Steps to reproduce *
v15 Beta sources
initalize a cluster ( ./initdb -D d1)
initalize another cluster ( ./initdb -D d2)
run pg_upgrade with -c option  ( ./pg_upgrade -d d1 -D d2 -b . -B . -c -v)
run pg_upgrade without -c option ( ./pg_upgrade -d d1 -D d2 -b . -B .)
--
--
--
Error


This behavior was not there in earlier released versions, i guess.
Is it expected behavior now onwards?

-- 
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company


--------------C62F7F15D2FCDAF8EB5DD47E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Hi,<br>
    <br>
    While performing pg_upgrade from v15Beta binaries/source, <br>
    I got this error below error <br>
    <br>
    could not create directory "d2/pg_upgrade_output.d": File exists<br>
    Failure, exiting<br>
    <br>
    <br>
    <b>Steps to reproduce </b><br>
    v15 Beta sources<br>
    initalize a cluster ( ./initdb -D d1)<br>
    initalize another cluster ( ./initdb -D d2)<br>
    run pg_upgrade with -c option  ( ./pg_upgrade -d d1 -D d2 -b . -B .
    -c -v)<br>
    run pg_upgrade without -c option ( ./pg_upgrade -d d1 -D d2 -b . -B
    .) <br>
    --<br>
    --<br>
    --<br>
    Error <br>
    <br>
    <br>
    This behavior was not there in earlier released versions, i guess. <br>
    Is it expected behavior now onwards?<br>
    <pre class="moz-signature" cols="72">-- 
regards,tushar
EnterpriseDB  <a class="moz-txt-link-freetext" href="https://www.enterprisedb.com/">https://www.enterprisedb.com/</a>
The Enterprise PostgreSQL Company 
</pre>
  </body>
</html>

--------------C62F7F15D2FCDAF8EB5DD47E--