Release Notes Qlik Sense PostgreSQL installer version 1.3.0 (May 2023)

[Sebastian_Linser]

The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.3.0.

Improvement / Defect	Details
SHEND-1261: Allow upgrade from the bundled postgres version 12.5 to 14.8 version using QPI	You can now update the embedded Qlik Sense Repository Database from versions 9.6 and 12.5 to version 14.8. (This is due to the following security issues of PostgreSQL)
SHEND-971: Allow custom Qlik Sense Installation Folder for use with QPI	When Qlik Sense is installed outside of the standardfolder C:\Program Files\Qlik\Sense e.g. (D:\Qlik\Sense), QPI can now be used to migrate the database.
QB-17384: Users were allowed to create folder names which are not allowed in Windows	Fixed the issue that it was possible to create a folder with the following charaters  (/,:,*,?,",<,>,|) which are not approved by Windows.

Known Limitations:

• Silent installation or upgrade is not available
• Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
  • Uninstall all patches before using QPI or
  • Upgrade to an IR release of Qlik Sense which supports QPI
• The summary of Database settings during the upgrade shows not the actual values of the pg_hba.conf
• Rollback is not available
• Database size is not checked against free disk space before a backup is taken.
• Supported are only upgrades of a Qlik Sense Repository Database installed as an embedded Database with the initial installation. You can not upgrade a standalone or QPI converted/installed database.
• QB-15164: Certain strings and characters cannot be used in the installation with QPI, the command line option for Postgres will not parse them in the command prompt. We have blocked & $ " @ ^ § to be used in the dialogue. If you run into that issue, please change the password to a simpler one before the use of QPI, you can change it back right after the upgrade. (This is anticipated to be fixed in 1.4.0).
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

To download the Qlik PostgreSQL installer and review the mandatory documentation, see Upgrading Qlik Sense Repository Database from PostgreSQL 9.6 to 12.5.

Related Content:

Upgrading Qlik Sense Repository Database from PostgreSQL 9.6 to 12.5 
Qlik Sense upgrade to November 2022 fails with "An existing standalone PostgresSQL v 12 database has... 

[Sebastian_Linser]

Improvement / Defect	Details
SHEND-1261: Allow upgrade from the bundled postgres version 12.5 to 14.8 version using QPI	You can now update the embedded Qlik Sense Repository Database from versions 9.6 and 12.5 to version 14.8. (This is due to the following security issues of PostgreSQL)
SHEND-971: Allow custom Qlik Sense Installation Folder for use with QPI	When Qlik Sense is installed outside of the standardfolder C:\Program Files\Qlik\Sense e.g. (D:\Qlik\Sense), QPI can now be used to migrate the database.
QB-17384: Users were allowed to create folder names which are not allowed in Windows	Fixed the issue that it was possible to create a folder with the following charaters  (/,:,*,?,",<,>,|) which are not approved by Windows.

Known Limitations:

• Silent installation or upgrade is not available
• Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
  • Uninstall all patches before using QPI or
  • Upgrade to an IR release of Qlik Sense which supports QPI
• The summary of Database settings during the upgrade shows not the actual values of the pg_hba.conf
• Rollback is not available
• Database size is not checked against free disk space before a backup is taken.
• Supported are only upgrades of a Qlik Sense Repository Database installed as an embedded Database with the initial installation. You can not upgrade a standalone or QPI converted/installed database.
• QB-15164: Certain strings and characters cannot be used in the installation with QPI, the command line option for Postgres will not parse them in the command prompt. We have blocked & $ " @ ^ § to be used in the dialogue. If you run into that issue, please change the password to a simpler one before the use of QPI, you can change it back right after the upgrade. (This is anticipated to be fixed in 1.4.0).
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

To download the Qlik PostgreSQL installer and review the mandatory documentation, see Upgrading Qlik Sense Repository Database from PostgreSQL 9.6 to 12.5.

Related Content:

Upgrading Qlik Sense Repository Database from PostgreSQL 9.6 to 12.5 
Qlik Sense upgrade to November 2022 fails with "An existing standalone PostgresSQL v 12 database has... 

[tvolkmerwolf]

Hello Sebastian,
many thanks for this. 

One question: regarding QB-15164 (special chars in superuser pw), do you know if the '@'-char is also blocked?

Thanks again and best wishes.

[Sebastian_Linser]

Hello @tvolkmerwolf Yes that one is also blocked for the moment i updated the item above. We are working on a better solution with the next QPI release. 

[tens]

Hi, 

And what about the '|', '+',  '=' characters ?

Because I got this kind of error and installer tell that backup failed.

Qlik.PostgreSQL.Installer.Utility.Exceptions.InstallPostgreSqlExecutableTaskFailedException: PostgreSQL installation failed with Exit code: 255. See installer logs for more details.
at Qlik.PostgreSQL.Installer.Utility.InstallerTask.InstallPostgreSqlExecutableTask.SilentInstallExecutable(String pathToExecutable, String baseDirectory, InstallerFlowContext context)
--- End of inner exception stack trace ---
at Qlik.PostgreSQL.Installer.Utility.InstallerTask.InstallPostgreSqlExecutableTask.SilentInstallExecutable(String pathToExecutable, String baseDirectory, InstallerFlowContext context)
at Qlik.PostgreSQL.Installer.Utility.InstallerTask.InstallPostgreSqlExecutableTask.Execute(InstallerFlowContext context)
at Qlik.PostgreSQL.Installer.Utility.InstallerTasksFlow.InstallerTaskExecutor.Execute(Queue`1 tasks, InstallerFlowContext context) 

[ktancula]

Is there any plan in QPI version 1.4 to add support for upgrading the database server to v14 if previously the upgrade from 9.6 to 12 was via QPI ?

[Sonja_Bauernfeind]

Hello @ktancula 

While it is being considered, QPI 1.4 will not have this feature. I recommend logging an idea/feature request.

All the best,
Sonja

[aldo-tgh]

Dear @Sonja_Bauernfeind ,

Is it possible to upgrade a PostgreSQL instance (11.x to 14.8) on a standalone server (clustered deployment) using QPI 1.3.0?

Aldo.

[Sebastian_Linser]

Hello @aldo-tgh ,

No QPI has just been developed to move the Qlik Sense Repository Database installed instance into a standalone one. It does not support the migration from a  standalone Database to another standalone Database.

best regards

Sebastian

[Skage]

Hi @Sebastian_Linser 

If the issue with special characters in passwords can/might be handled in a future version of QPI, would it be enough to set the pg_hba.conf to trust before attempting the migration and then set it back to md5 after completion and before starting any Qlik services?

I've made countless unbundlings with special characters and this only the 2nd time I've seen this message. I can't figure out what these two have in common and differ from the successful ones.

Most instructions are about lost passwords, but I know the pw so I'd rather keep the current pw if possible.

/lars

[Sebastian_Linser]

@Skage that is one way we found another, which we hope to be able to release soon, once the final release testing for QPI 1.4  is done.