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.
Bug 1889660 - [DDF] Please add an indication about which user to use for this step.
Summary: [DDF] Please add an indication about which user to use for this step.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: Documentation
Version: 8.0
Hardware: All
OS: All
high
unspecified
Target Milestone: rc
: 8.0
Assignee: Lenka Špačková
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 10:41 UTC by Direct Docs Feedback
Modified: 2021-05-31 11:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-31 11:43:50 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Direct Docs Feedback 2020-10-20 10:41:54 UTC
Please add an indication about which user to use for this step.
Should the DB be initialized as root or postgres user?
Is it recommended to create additional users?

Reported by: bram.mertens

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/deploying_different_types_of_servers/using-databases#annotations:cd14667d-d415-418a-8d00-e481cf5cfb9b

Comment 4 Patrik Novotný 2021-03-19 13:09:39 UTC
By default, the `postgresql-setup --initdb` initialises data in the RH recommended directory. This is independent from the current working directory when issuing this command.

Any `postgresql-setup` command is to be run as `root`. The script itself runs specific tasks required to be run as the `postgres` user under this user itself (via `su postgres -c [command]`) internally.

Comment 5 Lenka Špačková 2021-03-19 15:03:20 UTC
We are currently working on rewriting the procedures to clarify information about users.

Comment 8 Lenka Špačková 2021-05-31 11:43:50 UTC
The Using PostgreSQL part has been rewritten. Instructions about users have been added to the respective procedures. A new chapter about PostgreSQL users have been added.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/deploying_different_types_of_servers/index#using-postgresql
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/deploying_different_types_of_servers/index#con_postgresql-users_using-postgresql

Thanks again for your valuable feedback!


Note You need to log in before you can comment on or make changes to this bug.