Re: [GENERAL] log_filename - Mailing list pgsql-general

From basti
Subject Re: [GENERAL] log_filename
Date
Msg-id 85c000ba-8652-6969-dd8f-5a1051173701@unix-solution.de
Whole thread Raw
In response to Re: [GENERAL] log_filename  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
List 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@localhost ~]$
>>> [postgres@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@localhost ~]$
>>>
>>
>>
>


pgsql-general by date:

Previous
From: basti
Date:
Subject: Re: [GENERAL] log_filename
Next
From: Luca Looz
Date:
Subject: [GENERAL] UPDATE column without FK fires other FK triggers constraint check