Hi,

Actually I tried other work around but I think the installer is SMART ,and I install using default collation on the other 2x cluster (3 x in total), and the installer seems DETECT my installed instance’s collation and use it as the default.

One thing I found out which is not ok is, after I pg_upgrade PostgreSQL 11.14 to 13.4 today using

"D:\Program Files\PostgreSQL\13\bin\pg_upgrade.exe" --old-bind

ir="D:\Program Files\PostgreSQL\11\bin" --new-bindir="D:\Program Files\PostgreSQ

L\13\bin" --old-datadir="D:\Program Files\PostgreSQL\11\data" --new-datadir="D:\

Program Files\PostgreSQL\13\data" -U postgres --old-port=5434 --new-port=5435 -c

-k

And I got this message:

Performing Consistency Checks

-----------------------------

Checking cluster versions                                   ok

Checking database user is the install user                  ok

Checking database connection settings                       ok

Checking for prepared transactions                          ok

Checking for system-defined composite types in user tables  ok

Checking for reg* data types in user tables                 ok

Checking for contrib/isn with bigint-passing mismatch       ok

Checking for tables WITH OIDS                               ok

Checking for invalid "sql_identifier" user columns          ok

Creating dump of global objects                             ok

Creating dump of database schemas

                                                            ok

Checking for presence of required libraries                 ok

Checking database user is the install user                  ok

Checking for prepared transactions                          ok

Checking for new cluster tablespace directories             ok

If pg_upgrade fails after this point, you must re-initdb the

new cluster before continuing.

Performing Upgrade

------------------

Analyzing all rows in the new cluster                       ok

Freezing all rows in the new cluster                        ok

Deleting files from new pg_xact                             ok

Copying old pg_xact to new server                           ok

Setting oldest XID for new cluster                          ok

Setting next transaction ID and epoch for new cluster       ok

Deleting files from new pg_multixact/offsets                ok

Copying old pg_multixact/offsets to new server              ok

Deleting files from new pg_multixact/members                ok

Copying old pg_multixact/members to new server              ok

Setting next multixact ID and offset for new cluster        ok

Resetting WAL archives                                      ok

Setting frozenxid and minmxid counters in new cluster       ok

Restoring global objects in the new cluster                 ok

Restoring database schemas in the new cluster

                                                            ok

Adding ".old" suffix to old global/pg_control               ok

If you want to start the old cluster, you will need to remove

the ".old" suffix from D:/Program Files/PostgreSQL/11/data/global/pg_control.old

.

Because "link" mode was used, the old cluster cannot be safely

started once the new cluster has been started.

Linking user relation files

                                                            ok

Setting next OID for new cluster                            ok

Sync data directory to disk                                 ok

Creating script to analyze new cluster                      ok

Creating script to delete old cluster                       ok

Checking for extension updates                              notice

Your installation contains extensions that should be updated

with the ALTER EXTENSION command.  The file

    update_extensions.sql

when executed by psql by the database superuser will update

these extensions.

Upgrade Complete

And after that PostgreSQL 11 is not working at all but PostgreSQL 13, so I change back D:/Program Files/PostgreSQL/11/data/global/pg_control.old to D:/Program Files/PostgreSQL/11/data/global/pg_control

And then PostgreSQL 11 is fine, however , once I change pg_control.old to pg_control, my PostgreSQL 13 is not working any more even windows service started (I can’t login back to PostgreSQL 13 using UI tools)

Any reason why once I change the file name above for postgreSQL 11, PostgreSQL 13 is not working any more?

And in the same box I have one more PostgreSQL 9.5.x installed.

So now only 9.5 and 11.14 is running on my box, but I also want 13.4 up and running too ! how to fix this?

Sent from Mail for Windows

From: Sandeep Thakkar
Sent: Monday, 22 November 2021 5:53 pm
To: marrow.yung@gmail.com; PostgreSQL mailing lists
Subject: Re: BUG #17286: Installing open source edition of PostgreSQL 11.14 will fail

Hi

Installer will allow you to create only one cluster by default. If you want more than one server instance, then the best option would be to manually execute the initdb and start the services

On Wed, Nov 17, 2021 at 3:36 PM PG Bug reporting form <noreply@postgresql.org> wrote:

The following bug has been logged on the website:

Bug reference:      17286
Logged by:          Marrow Yung
Email address:      marrow.yung@gmail.com
PostgreSQL version: 11.14
Operating system:   windows server
Description:       

when install open source edition of PostgreSQL 11.14 on top of a Window
server 2012 R2 box which ALREADY has a earlier version of PostgreSQL
installed with collation other than default one, the installation of
PostgreSQL 11.14 or other version ALSO will collation other than the default
one, the installer will fail and no PostgreSQL windows service will be
installed.

the second PostgreSQL installation only works if it use default collation
.
I want more than one PostgreSQL instance on the SAME windows server box to
use other collation , e.g. traditional chinese (Hong Kong)

--

Sandeep Thakkar