Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 542C112B652F for ; Tue, 7 Feb 2012 16:41:03 -0400 (AST) Received: from nm26-vm0.bullet.mail.sp2.yahoo.com ([98.139.91.230]) by makus.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1RurqX-0002XM-Tl for pgsql-admin@postgresql.org; Tue, 07 Feb 2012 20:41:03 +0000 Received: from [98.139.91.62] by nm26.bullet.mail.sp2.yahoo.com with NNFMP; 07 Feb 2012 20:40:49 -0000 Received: from [98.139.91.23] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 07 Feb 2012 20:39:49 -0000 Received: from [127.0.0.1] by omp1023.mail.sp2.yahoo.com with NNFMP; 07 Feb 2012 20:39:49 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 29370.46783.bm@omp1023.mail.sp2.yahoo.com Received: (qmail 17438 invoked by uid 60001); 7 Feb 2012 20:39:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1328647188; bh=CFsJdSD020qXHx7Iot2+Pq07eLufUkQqajpxEWFbjcY=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AzRnHEaNpf8GTbDYWl74181CbDsslgaacXNZuFW3Sxz5CxJVXNpE47Y7XpWfQ80ECrw+8fo7dVKhfPT7pQyS0DidS7Aukj6cRWPfW337JKWPt4J+UuYIVgeN0XXXv9q0syi6oK9pFqEjONiGWUOO8TQQC0PbPu3AEyFOAY5Oi7o= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Revcq/9PS+QJYj8y5fSxzk3hw0jCcvhoXY4DTUKWdlhsHf0lVqHD6Q/zrwXysEF7Sm7V+4X7HyAXo9Z3i7hqn8t4w8+JTUOPQUxR1CWypAwZOF/mCqtA/CBCzFijKqNe5AqMCFALN+RbWf435moH3rczPQf7drdHkXBihK4S/wU=; X-YMail-OSG: QN89YR8VM1kDall0hh3hU5OyZuQ26hQ6m_YrQFa1uzJZkh1 Pdr41FLJaCDXp7OaVCofb9WblPhB8UoktMZO77Tm5aC_I1d9qtz8pxg4G7qs AW0yW0KxiWdkOOFKUCi1Pn2Wg2I9.NOSDP2D4oFAclfuVHtoKGMQITGIfDiG vMcNy6hPyj5ZkKp6S6aRGBsf4UnfxK7WjKGRKKa3C3NpCcrcLL..AL1dV16e hg9VJpOG.VyskCgAjDW08fehsqfU9dlwf.cwWPOqHwEKh8a2pi3b82jOJSNK WDWPgLU8IBr7I2hdyF4Bl2A_EKR2yDgXxeC4zMvbRDE24Un4KFTE_bIqOLL7 mRND4DGEiuoo0yBamqbPBnfgPXqySH19mtwDRlU1rS9JM8TF1Kr_4crPiohz zTJ0tFY96e9eqHfGBq.k- Received: from [206.80.5.2] by web46113.mail.sp1.yahoo.com via HTTP; Tue, 07 Feb 2012 12:39:48 PST X-Mailer: YahooMailWebService/0.8.116.338427 References: <1328640207.42210.YahooMailNeo@web46103.mail.sp1.yahoo.com> Message-ID: <1328647188.16397.YahooMailNeo@web46113.mail.sp1.yahoo.com> Date: Tue, 7 Feb 2012 12:39:48 -0800 (PST) From: Greg Williamson Reply-To: Greg Williamson Subject: Re: postgres 9.0 date aberration in logs To: Matheus de Oliveira Cc: "pgsql-admin@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: 0.5 (/) X-Archive-Number: 201202/43 X-Sequence-Number: 39103 Matheus --=0A=0A>=0A>To me seems that it just appended the data to your log= . To avoid this set the log_truncate_on_rotation to on, but notice that it = will replace the old logs.=0A>=0A>=0A=0A=0AThanks for the suggestion, but w= e seem to be using this already:=0A=0A-bash-3.2$ grep =A0log_truncate_on_ro= tation =A0postgresql.conf=0Alog_truncate_on_rotation =3D on# If on, an exis= ting log file of the=0A=0AIs it possible that this fails under some conditi= ons ?=A0=0A=0AWe are migrating to 9.1, which unfortunately showed the same = issues at almost the same time; no complaints in system logs or restarts of= the servers.=0A=0AVery odd ...=0A=0AGreg W.=0A