RE: BUG #17286: Installing open source edition of PostgreSQL 11.14 will fail

From: <marrow(dot)yung(at)gmail(dot)com>
To: Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: BUG #17286: Installing open source edition of PostgreSQL 11.14 will fail
Date: 2021-11-22 17:29:42
Message-ID: FC6FB60B-E2BF-46E5-8EAD-3657DF493D4F@hxcore.ol
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\(at)DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-HK link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=EN-US>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US>One thing I found out which is not ok is, after I pg_upgrade PostgreSQL 11.14 to 13.4 today using </span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&quot;D:\Program Files\PostgreSQL\13\bin\pg_upgrade.exe&quot; --old-bind</p><p class=MsoNormal>ir=&quot;D:\Program Files\PostgreSQL\11\bin&quot; --new-bindir=&quot;D:\Program Files\PostgreSQ</p><p class=MsoNormal>L\13\bin&quot; --old-datadir=&quot;D:\Program Files\PostgreSQL\11\data&quot; --new-datadir=&quot;D:\</p><p class=MsoNormal>Program Files\PostgreSQL\13\data&quot; -U postgres --old-port=5434 --new-port=5435 -c</p><p class=MsoNormal> -k</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>And I got this message:</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Performing Consistency Checks</p><p class=MsoNormal>-----------------------------</p><p class=MsoNormal>Checking cluster versions                                   ok</p><p class=MsoNormal>Checking database user is the install user                  ok</p><p class=MsoNormal>Checking database connection settings                       ok</p><p class=MsoNormal>Checking for prepared transactions                          ok</p><p class=MsoNormal>Checking for system-defined composite types in user tables  ok</p><p class=MsoNormal>Checking for reg* data types in user tables                 ok</p><p class=MsoNormal>Checking for contrib/isn with bigint-passing mismatch       ok</p><p class=MsoNormal>Checking for tables WITH OIDS                               ok</p><p class=MsoNormal>Checking for invalid &quot;sql_identifier&quot; user columns          ok</p><p class=MsoNormal>Creating dump of global objects                             ok</p><p class=MsoNormal>Creating dump of database schemas</p><p class=MsoNormal>                                                            ok</p><p class=MsoNormal>Checking for presence of required libraries                 ok</p><p class=MsoNormal>Checking database user is the install user                  ok</p><p class=MsoNormal>Checking for prepared transactions                          ok</p><p class=MsoNormal>Checking for new cluster tablespace directories             ok</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>If pg_upgrade fails after this point, you must re-initdb the</p><p class=MsoNormal>new cluster before continuing.</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Performing Upgrade</p><p class=MsoNormal>------------------</p><p class=MsoNormal>Analyzing all rows in the new cluster                       ok</p><p class=MsoNormal>Freezing all rows in the new cluster                        ok</p><p class=MsoNormal>Deleting files from new pg_xact                             ok</p><p class=MsoNormal>Copying old pg_xact to new server                           ok</p><p class=MsoNormal>Setting oldest XID for new cluster                          ok</p><p class=MsoNormal>Setting next transaction ID and epoch for new cluster       ok</p><p class=MsoNormal>Deleting files from new pg_multixact/offsets                ok</p><p class=MsoNormal>Copying old pg_multixact/offsets to new server              ok</p><p class=MsoNormal>Deleting files from new pg_multixact/members                ok</p><p class=MsoNormal>Copying old pg_multixact/members to new server              ok</p><p class=MsoNormal>Setting next multixact ID and offset for new cluster        ok</p><p class=MsoNormal>Resetting WAL archives                                      ok</p><p class=MsoNormal>Setting frozenxid and minmxid counters in new cluster       ok</p><p class=MsoNormal>Restoring global objects in the new cluster                 ok</p><p class=MsoNormal>Restoring database schemas in the new cluster</p><p class=MsoNormal>                                                            ok</p><p class=MsoNormal>Adding &quot;.old&quot; suffix to old global/pg_control               ok</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>If you want to start the old cluster, you will need to remove</p><p class=MsoNormal>the &quot;.old&quot; suffix from D:/Program Files/PostgreSQL/11/data/global/pg_control.old</p><p class=MsoNormal>.</p><p class=MsoNormal>Because &quot;link&quot; mode was used, the old cluster cannot be safely</p><p class=MsoNormal>started once the new cluster has been started.</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Linking user relation files</p><p class=MsoNormal>                                                            ok</p><p class=MsoNormal>Setting next OID for new cluster                            ok</p><p class=MsoNormal>Sync data directory to disk                                 ok</p><p class=MsoNormal>Creating script to analyze new cluster                      ok</p><p class=MsoNormal>Creating script to delete old cluster                       ok</p><p class=MsoNormal>Checking for extension updates                              notice</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Your installation contains extensions that should be updated</p><p class=MsoNormal>with the ALTER EXTENSION command.  The file</p><p class=MsoNormal>    update_extensions.sql</p><p class=MsoNormal>when executed by psql by the database superuser will update</p><p class=MsoNormal>these extensions.</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm'><p class=MsoNormal style='border:none;padding:0cm'>Upgrade Complete</p></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>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</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>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)</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Any reason why once I change the file name above for postgreSQL 11, PostgreSQL 13 is not working any more?</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>And in the same box I have one more PostgreSQL 9.5.x installed.</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>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?</p><p class=MsoNormal><b><o:p>&nbsp;</o:p></b></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:sandeep(dot)thakkar(at)enterprisedb(dot)com">Sandeep Thakkar</a><br><b>Sent: </b>Monday, 22 November 2021 5:53 pm<br><b>To: </b><a href="mailto:marrow(dot)yung(at)gmail(dot)com">marrow(dot)yung(at)gmail(dot)com</a>; <a href="mailto:pgsql-bugs(at)lists(dot)postgresql(dot)org">PostgreSQL mailing lists</a><br><b>Subject: </b>Re: BUG #17286: Installing open source edition of PostgreSQL 11.14 will fail</p></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=MsoNormal>Hi</p></div><div><p class=MsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=MsoNormal>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</p></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=MsoNormal>On Wed, Nov 17, 2021 at 3:36 PM PG Bug reporting form &lt;<a href="mailto:noreply(at)postgresql(dot)org">noreply(at)postgresql(dot)org</a>&gt; wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:4.8pt'>The following bug has been logged on the website:<br><br>Bug reference:&nbsp; &nbsp; &nbsp; 17286<br>Logged by:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Marrow Yung<br>Email address:&nbsp; &nbsp; &nbsp; <a href="mailto:marrow(dot)yung(at)gmail(dot)com">marrow(dot)yung(at)gmail(dot)com</a><br>PostgreSQL version: 11.14<br>Operating system:&nbsp; &nbsp;windows server<br>Description:&nbsp; &nbsp; &nbsp; &nbsp; <br><br>when install open source edition of PostgreSQL 11.14 on top of a Window<br>server 2012 R2 box which ALREADY has a earlier version of PostgreSQL<br>installed with collation other than default one, the installation of<br>PostgreSQL 11.14 or other version ALSO will collation other than the default<br>one, the installer will fail and no PostgreSQL windows service will be<br>installed.<br><br>the second PostgreSQL installation only works if it use default collation<br>.<br>I want more than one PostgreSQL instance on the SAME windows server box to<br>use other collation , e.g. traditional chinese (Hong Kong)</p></blockquote></div><p class=MsoNormal><br clear=all></p><div><p class=MsoNormal><o:p>&nbsp;</o:p></p></div><p class=MsoNormal>-- </p><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><span style='font-size:10.0pt;color:black'>Sandeep Thakkar</span></p></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

Attachment Content-Type Size
unknown_filename text/html 12.0 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2021-11-22 17:59:14 Re: BUG #17255: Server crashes in index_delete_sort_cmp() due to race condition with vacuum
Previous Message Tom Lane 2021-11-22 17:05:43 Re: PG 14.1 psql: symbol lookup error: psql: undefined symbol: PQmblenBounded