Обсуждение: Logfile removal

Hi,

I have run postmaster with -l option. When postmaster is running, i have
removed the logfile accidentally. I am unable to restart postmaster now
due to various other reasons.  Do i have to recreate the logfile? What are
all the problems the removal of logfile would create?

TIA.

regards,
bhuvaneswaran

On Wed, May 21, 2003 at 11:04:39AM +0530, A.Bhuvaneswaran wrote:

> I have run postmaster with -l option. When postmaster is running, i have
> removed the logfile accidentally.

Define "logfile".  Do you mean the pg_xlog?  If no, then your
start-up script will presumably create the log file for you when you
re-start.  If yes, however, then. . .

> I am unable to restart postmaster now
> due to various other reasons.

. . .it's not only other reasons.  You'll need to run pg_resetxlog.
Keep in mind that you are likely to have a mess on your hands
afterwards.  In particular, there may be inconsistencies in your
data.  Read the relevant docs.

A

--
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110

"A.Bhuvaneswaran" <bhuvansql@myrealbox.com> writes:
> I have run postmaster with -l option. When postmaster is running, i have
> removed the logfile accidentally.

You mean the -l logfile (postmaster's stderr)?  This is harmless except
that you won't have any way to look at the logfile.

> I am unable to restart postmaster now due to various other reasons.

The only way to start seeing the entries again is to restart the
postmaster, so I'd counsel doing that as soon as feasible.

What's actually happened is that the logfile is still on your disk (and
growing all the time...) but there is no link left to it in your
filesystem.  The kernel knows the file is still referenced by the open
filetable entry held by the postmaster, so it won't delete the file till
the postmaster quits.  But you have no way to get at it.

            regards, tom lane