Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 4CBED1337B7B
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri, 15 Oct 2010 15:03:24 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 97455-10 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri, 15 Oct 2010 18:03:17 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from nm4.bullet.mail.sp2.yahoo.com (nm4.bullet.mail.sp2.yahoo.com
	[98.139.91.74])
	by mail.postgresql.org (Postfix) with SMTP id 41BAB133729E
	for <pgsql-admin@postgresql.org>; Fri, 15 Oct 2010 15:03:15 -0300 (ADT)
Received: from [98.139.91.69] by nm4.bullet.mail.sp2.yahoo.com with NNFMP;
	15 Oct 2010 18:03:14 -0000
Received: from [98.139.91.28] by tm9.bullet.mail.sp2.yahoo.com with NNFMP;
	15 Oct 2010 18:03:14 -0000
Received: from [127.0.0.1] by omp1028.mail.sp2.yahoo.com with NNFMP;
	15 Oct 2010 18:03:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 732510.7186.bm@omp1028.mail.sp2.yahoo.com
Received: (qmail 55969 invoked by uid 60001); 15 Oct 2010 18:03:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
	t=1287165793; bh=heZVPkZJdVxXFjdYUl3U0kanIB4D6unEqnxmqDKrbIE=;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
	b=u1KlIykhh5QxWFuvVwRS+Dwq3cduj+5hYIbEGBhINIrscASw2gKui+Zo+4qJfl7dBC3h3za345UHoBcJKu8fU9IiOFbZKF6mvpkMaf3a7/RrUs8Pc8AhP7A1b0kBIITA7TT1ZN1eMU5ndZ+jvNbYc5G2ush0Tl5pytweBv7U+7k=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
	b=X1a7fFKb9BZOhWS8msO725DIzC5I0OpLh63ZfWr4ZNvVQuQcJ/UCwV5auc0qzfJcY1DFvtjNIFfAOw2Zb3CfYI0GAnpW2eP1mEB+czQ7gDACrNsZuQGIwBi9N//BTV/0xVsE/OZSC952YXojcbvfm1OSQczgjEg/dAruwQawwGY=;
Message-ID: <165713.55278.qm@web111313.mail.gq1.yahoo.com>
X-YMail-OSG: A.4LmMwVM1nUMGmoAno7vbdNVkV1WRuPLuFAXxW.lFSg4_C
	eag.GIjsH3sk6B95SEHpF5Aq4ki9QvMGIGeBVLzOXd2Fw8Jq7kEINqnUz0Uv
	fHCQDwzmjPTUuO7KPdyXwsytzxz.wM1eESc5ijP8yvdJJlqafZqbBeGtmC25
	1SiVja_UTnAknLAX9T2G.Jyfvdump9yxy8AebvxayGFrR6z0iKRJ6KsHoiU1
	OpKm9ICpAkCbuC_4KUeW9tpWNU6raeK0-
Received: from [198.119.134.32] by web111313.mail.gq1.yahoo.com via HTTP;
	Fri, 15 Oct 2010 11:03:12 PDT
X-Mailer: YahooMailRC/504.5 YahooMailWebService/0.8.106.282862
References: <1287085384.1684.52.camel@tony1.localdomain>
	<F4C27E77F7A33E4CA98C19A9DC6722A2069F3459@EXCHANGE.corp.perceptron.com>
Date: Fri, 15 Oct 2010 11:03:12 -0700 (PDT)
From: Jessica Richard <rjessil@yahoo.com>
Subject: Postgres log file
To: pgsql-admin@postgresql.org
In-Reply-To: 
 <F4C27E77F7A33E4CA98C19A9DC6722A2069F3459@EXCHANGE.corp.perceptron.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1177897482-1287165792=:55278"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201010/128
X-Sequence-Number: 35869

--0-1177897482-1287165792=:55278
Content-Type: text/plain; charset=us-ascii

I am curious about this scenario:

What is going to happen when a server is running and the Postgres log file is 
accidentally deleted or renamed?  The server will have no place to write its log 
entries obviously.. what else?.

Is there any way to check within Postgres what the current log name (with a 
particular time stamp when rotated last time) is so that a file with a correct  
matching name can be manually created?

For this situation, what is the proper way to get the server to write to a new 
log file without having to bounce the Postgres server itself?

Thanks!


      
--0-1177897482-1287165792=:55278
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">I am curious about this scenario:<br><br>What is going to happen when a server is running and the Postgres log file is accidentally deleted or renamed?&nbsp; The server will have no place to write its log entries obviously.. what else?.<br><br>Is there any way to check within Postgres what the current log name (with a particular time stamp when rotated last time) is so that a file with a correct&nbsp; matching name can be manually created?<br><br>For this situation, what is the proper way to get the server to write to a new log file without having to bounce the Postgres server itself?<br><br>Thanks!<br><br><br></div><br>

      </body></html>
--0-1177897482-1287165792=:55278--