keeping a log / debug info

From: "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com>
To: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: keeping a log / debug info
Date: 2002-09-19 15:53:04
Message-ID: 73309C2FDD95D11192E60008C7B1D5BB04C73F7A@snt452.corp.bcbsm.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Howdy:

Running PostgreSQL 7.2.1 on RedHat Linux 7.2 kernel 2.4.7.

I am running postgres with a '-d' option (debug)
and storing that info in a log file. This morning
I moved the log file (trying to gzip it) and touched
a new version of that file ... (didn't mean to do that).
Now no data is being recorded ...

Can I restart the database without losing backends
that currently exist? Sort of a -HUP postmaster<pid>?

Is there a way to record this info via /etc/syslog.conf
and have the system do it? (for instance, the message file ...
when it gets so large, it is moved to message.0
and you see a *new* message file).

Thanks!

-X

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Johnson, Shaunn 2002-09-19 15:55:18 Re: killing process question
Previous Message Tom Lane 2002-09-19 15:49:39 Re: killing process question