------------------------------------------------------------------------------- Fix Number: FJSVfsep-POOL2-16-1601-0.el8.s390x Product Names and Versions: FUJITSU Enterprise Postgres Pgpool-II 16 *1 *1 It is bundled to the server package of the following product. Fujitsu Software Enterprise Postgres Advanced Edition 16 for Linux on Z Creation date: 10.09.2024 ------------------------------------------------------------------------------- [High Risk Activity] The Customer acknowledges and agrees that the Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. The Customer, shall not use the Product without securing the sufficient safety required for the High Safety Required Use. In addition, Fujitsu (or other affiliate's name) shall not be liable against the Customer and/or any third party for any claims or damages arising in connection with the High Safety Required Use of the Product. Product and company names mentioned in this manual are the trademarks or registered trademarks of their respective owners. Copyright 2024 FUJITSU LIMITED ------------------------------------------------------------------------------- [Notes] - This is the readme for RHEL 8. - This fix is applicable to environments where the following are installed. FUJITSU Enterprise Postgres Pgpool-II 16 - Please ensure that the following steps are carried out before applying or deleting this patch. - Do not set the library path of FUJITSU Enterprise Postgres (*1) to the environment variable(*2). (*1) /lib (*2) LD_LIBRARY_PATH and LD_LIBRARY_PATH_32. - Stop the running Pgpool-II. - If the application and restoration of this correction fail, collect the following materials and contact our technical staff. - /var/log/fsep_POOL2_1601_patch.log - /var/opt/FJSVfupde/log (All files in log directory) - Perform a recovery procedure of return to the pre-apply and pre-restore state if. 1) Failed to apply or restore this fix. and 2) The following log files exist. and /var/log/fsep_POOL2_1601_patch.log 3) The log file ends with one of the following. ROLLBACK(U): was failed(non-0 return value). ROLLBACK(I): was failed(non-0 return value). [Recovery procedure] 1) Run the following command to switch to the superuser on the system. $ su - Password:****** 2) Verify that the package is installed by running the following command. If it was not installed, run of "4)". # rpm -q FJSVfsep-POOL2-16 3) Run the following command to uninstall the package. # rpm -e FJSVfsep-POOL2-16 --nodeps To confirm the uninstallation, run the following command. # rpm -q FJSVfsep-POOL2-16 4) Run the following command to install the package. # cd /PKG # rpm -i FJSVfsep-POOL2-16-*.rpm(*1) \ --prefix= --nodeps 5) To confirm the installation, run the following command. # rpm -q FJSVfsep-POOL2-16 (*1)File names are different on apply failure and restore failure. ------------------------------------------------------------------------------- [Patch Description] The following fixes are included in this patch: Fix Number: FJSVfsep-POOL2-16-1601-0.el8.s390x 01 PH24017 [ ]Security failure [*]Serious failure ([ ]Degradation) [ ]Incompatibility does not exist / [*]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description There is no particular issue because bug corrections in Pgpool-II 4.5.1, 4.5.2 apply to FUJITSU Enterprise Postgres. - Requirements to reproduce this issue There is no particular condition because this fix applies the changes of Pgpool-II 4.5.1, 4.5.2 to FUJITSU Enterprise Postgres. You can see applied changes in the below URL. https://www.pgpool.net/docs/latest/en/html/release-4-5-1.html https://www.pgpool.net/docs/latest/en/html/release-4-5-2.html - Action Apply the changes of PostgreSQL 16 to FUJITSU Enterprise Postgres. - Compatibility Information - Summary Change the version of Pgpool-II that is shipped with Fujitsu Enterprise Postgres to 4.5.2. As a result, the following changes have been made: 1. The default values for recovery_user, failover_on_backend_shutdown, and insert_lock change. 2. It now checks whether an Extended Query Protocol message has been terminated, and raises a FATAL error if it has not. - Environment 1. 1) Apply emergency amendments including PH24017, and 2) For recovery_user, failover_on_backend_shutdown, and insert_lock If no settings have been made. 2. 1) Apply emergency amendments including PH24017. and 2) The application uses extended queries. and 3) For simple queries without terminating the extended query protocol message.If you send a protocol message. - Products combination of this compatibility problem If an emergency amendment including PH24017 is applied and the conditions specified in Occurrence Conditions apply. - Reason of conflictions This is due to a specification change due to an upgrade of Pgpool-II, which is included in Fujitsu Enterprise Postgres. - Impacts 1. The default values for recovery_user, failover_on_backend_shutdown, and insert_lock change. 2. Pgpool-II might behave differently in some cases. - Functional items (Summary, Before/After of migration) 1. The default values change to the values as documented. [Before] recovery_user='' failover_on_backend_shutdown=on insert_lock=off [After] recovery_user='nobody' failover_on_backend_shutdown=off insert_lock=on 2. [Before] A simple query could be executed even if the occurrence condition was met. [After] If the occurrence condition is met, a FATAL error occurs when executing a simple query. - Preventive Method 1. Specify an explicit value. 2. When using simple and extended queries, you should terminate the extended query message before executing the simple query. - Back out method of the functions None. - User action It is the same as the Preventive Method. 02 PH24035 [*]Security failure [*]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description This fix reflects fixes up to OpenSSL 3.0.14 in this product and does not indicate any specific symptoms. - Requirements to reproduce this issue This fix reflects fixes up to OpenSSL 3.0.14 in this product and has no specific occurrence conditions. The version of OpenSSL in which this product reflects the correction is as follows. - Enterprise Postgres 12, 12SP1, 12SP1A, 12SP1B, 13, 13SP1, 13SP1A 14, 14SP1,15, 15SP1, 15SP2 3.0.12 - Enterprise Postgres 16 3.0.13 - Symfoware Server V12.4.1, V12.5.0, V12.6.0, V12.6.0A, V12.7.0 3.0.12 To check the details of the changes up to OpenSSL 3.0.14, see the OpenSSL release notes. https://openssl-library.org/news/openssl-3.0-notes/ - Action Apply OpenSSL changes to the product. - Compatibility Information None. ------------------------------------------------------------------------------- [List of fixed files] Files replaced by the patch: $INSDIR $INSDIR/bin $INSDIR/bin/pcp_attach_node $INSDIR/bin/pcp_detach_node $INSDIR/bin/pcp_health_check_stats $INSDIR/bin/pcp_node_count $INSDIR/bin/pcp_node_info $INSDIR/bin/pcp_pool_status $INSDIR/bin/pcp_proc_count $INSDIR/bin/pcp_proc_info $INSDIR/bin/pcp_promote_node $INSDIR/bin/pcp_recovery_node $INSDIR/bin/pcp_reload_config $INSDIR/bin/pcp_stop_pgpool $INSDIR/bin/pcp_watchdog_info $INSDIR/bin/pg_enc $INSDIR/bin/pg_md5 $INSDIR/bin/pgpool $INSDIR/bin/pgpool_setup $INSDIR/bin/pgproto $INSDIR/bin/watchdog_setup $INSDIR/bin/wd_cli $INSDIR/etc $INSDIR/etc/aws_eip_if_cmd.sh.sample $INSDIR/etc/aws_rtb_if_cmd.sh.sample $INSDIR/etc/escalation.sh.sample $INSDIR/etc/failover.sh.sample $INSDIR/etc/follow_primary.sh.sample $INSDIR/etc/pcp.conf.sample $INSDIR/etc/pgpool.conf.sample $INSDIR/etc/pgpool_remote_start.sample $INSDIR/etc/pool_hba.conf.sample $INSDIR/etc/product.inf $INSDIR/etc/recovery_1st_stage.sample $INSDIR/etc/replication_mode_recovery_1st_stage.sample $INSDIR/etc/replication_mode_recovery_2nd_stage.sample $INSDIR/include $INSDIR/include/libpcp_ext.h $INSDIR/include/pcp.h $INSDIR/include/pool_process_reporting.h $INSDIR/include/pool_type.h $INSDIR/lib $INSDIR/lib/libcom_err.so.3 $INSDIR/lib/libcrypto.so $INSDIR/lib/libcrypto.so.3 $INSDIR/lib/libgssapi_krb5.so.2 $INSDIR/lib/libk5crypto.so.3 $INSDIR/lib/libkrb5.so.3 $INSDIR/lib/libkrb5support.so.0 $INSDIR/lib/liblber-2.5.so.0 $INSDIR/lib/libldap-2.5.so.0 $INSDIR/lib/libpcp.a $INSDIR/lib/libpcp.la $INSDIR/lib/libpcp.so $INSDIR/lib/libpcp.so.2 $INSDIR/lib/libpcp.so.2.0.0 $INSDIR/lib/libpq.so.5 $INSDIR/lib/libssl.so $INSDIR/lib/libssl.so.3 $INSDIR/share $INSDIR/share/pgpool-II $INSDIR/share/pgpool-II/insert_lock.sql $INSDIR/share/pgpool-II/pgpool.pam -------------------------------------------------------------------------------