Re: log_filename

From: basti <mailinglist(at)unix-solution(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: log_filename
Date: 2017-07-18 09:13:47
Message-ID: 85c000ba-8652-6969-dd8f-5a1051173701@unix-solution.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I want to create a generic own_postgres.conf and include that in
postgres.conf

I ask a bit wrong. Is there a variable to include postgres version on
log_filename?

Best regards
basti

Am 18.07.2017 um 10:40 schrieb Achilleas Mantzios:
> On 18/07/2017 11:36, Walter Nordmann wrote:
>> May be i'm blind: what did you really do? changed postgresql.conf?
>>
> He hardcoded it in the postgresql.conf .
>> regards
>> walter
>>
>>
>> Am 18.07.2017 um 10:31 schrieb Ahtesham Karajgi:
>>> Add the version in the log_filename itself.
>>>
>>> Below is the test case.
>>>
>>> naveed=# show log_filename ;
>>> log_filename
>>> --------------------------------
>>> postgresql-%Y-%m-%d_%H%M%S.log
>>> (1 row)
>>>
>>> naveed=# select pg_reload_conf();
>>> pg_reload_conf
>>> ----------------
>>> t
>>> (1 row)
>>>
>>> naveed=# show log_filename ;
>>> log_filename
>>> ------------------------------------
>>> postgresql-9.5-%Y-%m-%d_%H%M%S.log
>>> (1 row)
>>>
>>> test=# \q
>>> [postgres(at)localhost ~]$
>>> [postgres(at)localhost ~]$ ls -lrth /usr/local/pgsql/data/pg_log | tail -2
>>> -rw-------. 1 postgres postgres 3.3K Jul 18 01:25
>>> postgresql-2017-07-18_000000.log
>>> -rw-------. 1 postgres postgres 4.1K Jul 18 01:27
>>> postgresql-9.5-2017-07-18_012530.log
>>> [postgres(at)localhost ~]$
>>>
>>
>>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Luca Looz 2017-07-18 12:49:10 UPDATE column without FK fires other FK triggers constraint check
Previous Message basti 2017-07-18 08:57:06 Re: log_filename