RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

The postgresql init script is prepared to be copied (or symlinked) but it has
its local variable 'pidfile' defined like:

  pidfile="/var/run/postmaster.${PGPORT}.pid"

This makes the script differentiate lock files for separated instances just
based on the PGPORT.  If the PGPORT has the same value for more then one
postgres server, these init servers may not co-exist without additional changes
of the script.

The 'pidfile' variable should be ideally defined before sourcing per-instance
configuration file and reuse ${NAME} variable somehow.  Possibly this patch
would be usable:

  --- /etc/init.d/postgresql      2012-08-27 17:43:59.000000000 +0200
  +++ /etc/init.d/postgresqlnew   2013-08-13 10:27:04.509000246 +0200
  @@ -47,15 +47,15 @@
   # Value to set as postmaster process's oom_adj
   PG_OOM_ADJ=-17

  +lockfile="/var/lock/subsys/${NAME}"
  +pidfile="/var/run/postmaster.${PGPORT}.${NAME}.pid"
  +
   # Override defaults from /etc/sysconfig/pgsql if file is present
   [ -f /etc/sysconfig/pgsql/${NAME} ] && . /etc/sysconfig/pgsql/${NAME}

   export PGDATA
   export PGPORT

  -lockfile="/var/lock/subsys/${NAME}"
  -pidfile="/var/run/postmaster.${PGPORT}.pid"
  -
   script_result=0

   start(){

(In reply to Pavel Raiskup from comment #0)
> The postgresql init script is prepared to be copied (or symlinked) but it
> has its local variable 'pidfile' defined like:
> 
>   pidfile="/var/run/postmaster.${PGPORT}.pid"
> 
> This makes the script differentiate lock files for separated instances just
> based on the PGPORT.  If the PGPORT has the same value for more then one
> postgres server, these init servers may not co-exist without additional
> changes of the script.

FTR: RHSCL 2.0 (rh-postgresql94) has this fixed,
(pidfile="/var/run/${NAME}.pid").