Hernan Gonzalez wrote:
>Anyway, the 7.0.2 docs state (in the "pg_options" section)
>that :
>
>> Message printed to stdout or stderr are prefixed by a timestamp containi
>ng also the backend pid
>>
>> #timestamp #pid #message
>> 980127.17:52:14.173 [29271] StartTransactionCommand
>> 980127.17:52:14.174 [29271] ProcessUtility: dro
...
>It is very true that this format is useful, but that's not what I get.
>My 7.0.2 postmaster is started with stdout & stderr redirected to a file,
>and I get no timestamps no pids.
>
>My .../data/pg_options file contains two lines:
>
> verbose=1
> query
>
>Am I doing something wrong ?
It is a compilation option:
--- postgresql-7.0.2.orig/src/include/config.h.in
+++ postgresql-7.0.2/src/include/config.h.in
@@ -161,7 +161,8 @@
* ELOG_TIMESTAMPS: adds a timestamp with the following format to elog
* messages: yymmdd.hh:mm:ss.mmm [pid] message
*/
-/* #define ELOG_TIMESTAMPS */
+/* Turned on for Debian */
+#define ELOG_TIMESTAMPS
--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"For I am not ashamed of the gospel of Christ; for it
is the power of God unto salvation to every one that
believeth; to the Jew first, and also to the Greek."
Romans 1:16
