Bug 1145129 - Moving postgresql-setup, service file and README to separate tarball
Summary: Moving postgresql-setup, service file and README to separate tarball
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: postgresql
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1015431
TreeView+ depends on / blocked
 
Reported: 2014-09-22 12:38 UTC by Pavel Raiskup
Modified: 2014-09-22 13:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-22 13:34:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pavel Raiskup 2014-09-22 12:38:34 UTC
Starting from Fedora 22 (rawhide now), the downstream files postgresql-setup,
postgresql.service, README.rpm-dist and some others will be packaged from
separate tarball.  This results in non-trivial change in spec file and it is
worth having special bug for this change.  Possibly, some discussions or Q/A
may be done here.

Maintaining of those files is closely tight together (among all rpm packages
distributing PostgreSQL in RHEL/Fedora/RHSCL/PGDG) and fixing/enhancing of all
those files makes unnecessary traffic in Fedora's master git branch.

As the new postgresql-setup generating is now done separately, Fedora users
(and mainly developers of this script) may now easily run deafult Fedora
postgresql-* packages and install/test git version of postgresql-setup (and
relatives) via:

  $ ./configure --prefix=/usr
  $ make && make check
  $ sudo make install

This should be more comfortable.  Also, other systemd-using distributions may
use this code more easily which should result in better stability.

Comment 1 Pavel Raiskup 2014-09-22 12:49:55 UTC
The (temporary) git repository and release directory:
https://fedorapeople.org/cgit/praiskup/public_git/postgresql-setup.git/
https://praiskup.fedorapeople.org/proj/postgresql-setup/

Comment 3 Pavel Raiskup 2014-09-22 13:34:43 UTC
Some changes which come with this bug:

* when changing the default configuration,  users should not use .include
  statement in /etc/systemd/system/postgresql.service but rather use systemd
  drop-in feature (documented directly in postgresql.service file)

* we now distribute postgresql.service (the default, pre-configured instance
  of PostgreSQL server) and postgresql@.service, which allows users
  create another instance of PostgreSQL very easily by:

  postgresql-setup --initdb --unit=postgresql@secondary --new-systemd-unit \
     --port XXXX --datadir /var/lib/pgsql/data-secondary
  (documented in README.rpm-dist)

* postgresql-setup now recognizes now what is set by EnvironmentFile=


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