Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJaroslav Škarvada
2013-05-30 14:42:10 UTC
Description of problem:
There is the following text in the /usr/share/doc/postgresql-9.2.4/README.rpm-dist :
...
QUICKSTART
-----------------------------------------------------------------------------
For a fresh installation, you will need to initialize the cluster first. Run:
postgresql-setup initdb
as root, and it will prepare a new database cluster for you. Then you will
need to start PostgreSQL. Again as root, run:
systemctl start postgresql.service
This command will start a postmaster that willl listen on localhost and Unix
socket 5432 only. Edit /var/lib/pgsql/data/postgresql.conf and pg_hba.conf
if you want to allow remote access -- see the section on Grand Unified
Configuration.
You will probably also want to do
systemctl enable postgresql.service
...
But it doesn't work, e.g.:
# postgresql-setup initdb
bash: postgresql-setup: command not found
# systemctl start postgresql.service
Failed to issue method call: Unit postgresql.service failed to load: No such file or directory. See system logs and 'systemctl status postgresql.service' for details.
# systemctl start postgresql.service
Failed to issue method call: Unit postgresql.service failed to load: No such file or directory. See system logs and 'systemctl status postgresql.service' for details.
Also I cannot find package which provide these files.
Version-Release number of selected component (if applicable):
postgresql-9.2.4-1.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Check the /usr/share/doc/postgresql-9.2.4/README.rpm-dist from the postgresql package
Actual results:
The instructions are not usable
Expected results:
Correct instructions or the README.rpm-dist not packaged in
postgresql package.
Additional info:
I tried RHEL-7.0-20130529.n.1 compose.
Thanks for the report. That commands require postgresql-server package.
The package postgresql contains only client applications (see the
`rpm -qi postgresql` output). What about this simple fix of README file?
-QUICKSTART
+QUICKSTART (note that this requires postgresql-server installed)
(Moving the file to postgresql-server is not a correct).
Pavel
Comment 3Jaroslav Škarvada
2013-06-05 08:59:59 UTC
Hi Pavel,
the note would be great, but I would rather split the doc into two files, one for client one for server. I think it would be more clean. The current state is very confusing. It is distro specific doc, shipped out of the upstream archive, so I think it shouldn't be problem to update it / split it. Just add revision records there.
> the note would be great, but I would rather split the doc into two files,
> one for client one for server. I think it would be more clean. The current
> state is very confusing.
Agree, this is probably good idea.
> It is distro specific doc, shipped out of the upstream archive, so I think it
> shouldn't be problem to update it / split it. Just add revision records
> there.
I tried to find _current_ upstream source of README.rpm-dist file and (as I
don't see very deeply to history) I was unable to find that. Seems like the
current version is maintained just in RHEL/Fedora (and it is actually continued
original PGDG work).
CC'ing: Devrim, (as you are mentioned as a current author) do you think that
such split would be reasonable? Probably to names README.rpm-dist{,-server}?
Pavel
Hi,
Sorry for the late response (unrest in Turkey...)
Just committed the text change (wrt quickstart) to 9.3. I will backpatch it soon.
I am not in favor of splitting README file. The package names and descriptions are quite clear that -server subpackage is the *server* package.
Regards, Devrim
Description of problem: There is the following text in the /usr/share/doc/postgresql-9.2.4/README.rpm-dist : ... QUICKSTART ----------------------------------------------------------------------------- For a fresh installation, you will need to initialize the cluster first. Run: postgresql-setup initdb as root, and it will prepare a new database cluster for you. Then you will need to start PostgreSQL. Again as root, run: systemctl start postgresql.service This command will start a postmaster that willl listen on localhost and Unix socket 5432 only. Edit /var/lib/pgsql/data/postgresql.conf and pg_hba.conf if you want to allow remote access -- see the section on Grand Unified Configuration. You will probably also want to do systemctl enable postgresql.service ... But it doesn't work, e.g.: # postgresql-setup initdb bash: postgresql-setup: command not found # systemctl start postgresql.service Failed to issue method call: Unit postgresql.service failed to load: No such file or directory. See system logs and 'systemctl status postgresql.service' for details. # systemctl start postgresql.service Failed to issue method call: Unit postgresql.service failed to load: No such file or directory. See system logs and 'systemctl status postgresql.service' for details. Also I cannot find package which provide these files. Version-Release number of selected component (if applicable): postgresql-9.2.4-1.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Check the /usr/share/doc/postgresql-9.2.4/README.rpm-dist from the postgresql package Actual results: The instructions are not usable Expected results: Correct instructions or the README.rpm-dist not packaged in postgresql package. Additional info: I tried RHEL-7.0-20130529.n.1 compose.