| From: | Will Crawford <billcrawford1970(at)gmail(dot)com> |
|---|---|
| To: | Nigel Heron <nheron(at)querymetrics(dot)com> |
| Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, PostgreSQL Hackers ML <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Can we add sample systemd service file to git repo? |
| Date: | 2013-11-18 15:30:04 |
| Message-ID: | CAJDxst5_4kzTGx1YVUMzpWjWW7QgNrLqWO5SDAofpabfpjYVcQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12 November 2013 20:54, Nigel Heron <nheron(at)querymetrics(dot)com> wrote:
> On Tue, Nov 12, 2013 at 11:47 AM, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> wrote:
...
>> http://svn.pgrpms.org/browser/rpm/redhat/9.3/postgresql/F-19/postgresql-9.3.service is an example of what we use in the RPMs. (if website fails, please just reload)
>>
>> Attached is a modified version that will work with the compile defaults.
> Hi, should we put PGPORT in the systemd file without an easy way to override it?
> As an example, when yum updating minor versions on fedora 18 (using
> the yum.postgresql.org rpms), any changes to the systemd service file
> are overwritten by the new rpm and the port is forced back to 5432.
> This makes having pg9.2 and pg9.3 on the same box conflict after each
> minor version update.
IIRC there's a "%config(noreplace)" directive in the .spec that can
cause the new file to be saved with an extension (.rpmnew?) instead of
overwriting the old one.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-11-18 15:53:26 | Re: Freezing without write I/O |
| Previous Message | Robert Haas | 2013-11-18 15:26:55 | Re: Small improvement to json out functions by using cstring_to_text_with_len instead of cstring_to_text |