Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CFF2564FE8B for ; Sat, 20 Dec 2008 16:32:21 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 56120-04 for ; Sat, 20 Dec 2008 16:32:19 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mail.postgresql.org (Postfix) with ESMTP id EDF8664FE01 for ; Sat, 20 Dec 2008 16:32:18 -0400 (AST) Received: by yw-out-2324.google.com with SMTP id 3so520229ywj.73 for ; Sat, 20 Dec 2008 12:32:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=rwNkWaMLc+7XrpxDMchVeMAsmtR0AQmUy9Ddq7Ao+3M=; b=Gw46cQvrDA0g0CawiD4HTyd4w3DvtfRfa7L+CZzva4fiJK2Fyv9xCuohYttn6s6iyG ms7QQtnPQnjkwxh9j1ZjK9sFcYBNOS5u9L0paGBj28ff5OlS1Uf1yRFl4Z9CvOfqBXEm mZ0ZJC7A68W4BLIfgRhis1fA2aV/HiS0u6KiI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=C75pg42HxR2HuUH4xWnm1F49XNxRZBf+XFWoZNQ8nzL9TDhCe2NcDqXc2OT0fbjc9g 4CBIJjFLy4mFtljJcYrbxPx5f3/0VtrvMfNUYb+IEHqe3UwAyIF3YVpGO4Atr+0K8bai GOIvUv7or8Qc9hntptUv7oakAoMzZPXDAyhlY= Received: by 10.100.153.4 with SMTP id a4mr3023843ane.101.1229805137841; Sat, 20 Dec 2008 12:32:17 -0800 (PST) Received: by 10.100.107.2 with HTTP; Sat, 20 Dec 2008 12:32:17 -0800 (PST) Message-ID: <93f118f0812201232s5a5bf166y1701f940303a19f1@mail.gmail.com> Date: Sat, 20 Dec 2008 12:32:17 -0800 From: "Jennifer Redman" To: "John Lister" Subject: Re: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_44234_16927605.1229805137837" References: <93f118f0812181248s122a93d3vaa09831d64d9e6ae@mail.gmail.com> <93f118f0812181534w1f78f0a5tda3a21a7074b04e6@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200812/169 X-Sequence-Number: 31002 ------=_Part_44234_16927605.1229805137837 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sat, Dec 20, 2008 at 12:26 AM, John Lister wrote: > > > The pg_maintenance scripts check the state of the autovacuuum flag in the > postgres config files. If it is enabled they simply quit and don't do > anything. Disabling autovacuum causes them to run... So you can leave them > uncommented... Why would you want to continue to run a cron job that is: 1) No longer applicable to the current version of software (Postgresql 8.1+) 2) Throwing an error in your logs? The default behavior should be that this cron job is not active by default if one is running Postgresql 8.1+ > > > Although why it causes the "Incomplete start-up packet" messages is a > mystery... Because the Debian and Debian derivative packages (Ubuntu) of postgresql-common -- which is a required dependency for the main postgresql package, was not rev'd correctly when the autovaccuum feature was added by default into Postgresql. The script, pg_maintenance, is no longer functioning as was intended against the current version. This is a software bug, and I've filed bug reports in both the Debian and Ubuntu systems. A version check needs to happen on install of postgresql-common to determine the correct behavior of pg_maintenance based upon the version of PostgresSQL (patch exisiting package) or a new package needs to be created for postgresql 8.1+. In the meantime, if you are here because you want to know how to get rid of the 'incomplete start-up packet' message in your postgresql logs (thrown at the exact same interval as the referenced cron job) are running a derivative of Debian (not sure if this happens with other distros or OS's) comment out the cron job. Unfortunately, the message is still thrown when starting and stopping postgresql, since the init script in postgresql-common is also running the pg_maintenance check. Hopefully, a patch will fix. This is something much more reasonable to live with then a cron job that doesn't work running every 5 hours. Me, I like to bring up new systems with completely clean logs, and identify, fix any errors in those logs if running an existing system, and not run cron jobs that are not needed. ;> Regards, Jennifer ------=_Part_44234_16927605.1229805137837 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Sat, Dec 20, 2008 at 12:26 AM, John Lister <john.lister-ps@kickstone.com> wrote:


The pg_maintenance scripts check the state of the autovacuuum flag in the postgres config files. If it is enabled they simply quit and don't do anything. Disabling autovacuum causes them to run... So you can leave them uncommented...

Why would you want to continue to run a cron job that is:

1) No longer applicable to the current version of software (Postgresql 8.1+)

2) Throwing an error in your logs?

The default behavior should be that this cron job is not active by default if one is running Postgresql 8.1+
 


Although why it causes the "Incomplete start-up packet" messages is a mystery...


Because the Debian and Debian derivative packages (Ubuntu) of postgresql-common -- which is a required dependency for the main postgresql package, was not rev'd correctly when the autovaccuum feature was added by default into Postgresql.  The script, pg_maintenance, is no longer functioning as was intended against the current version.  This is a software bug, and I've filed bug reports in both the Debian and Ubuntu systems.

A version check needs to happen on install of postgresql-common to determine the correct behavior of pg_maintenance based upon the version of PostgresSQL (patch exisiting package) or a new package needs to be created for postgresql 8.1+.

In the meantime, if you are here because you want to know how to get rid of the 'incomplete start-up packet' message in your postgresql logs (thrown at the exact same interval as the referenced cron job) are running a derivative of Debian (not sure if this happens with other distros or OS's) comment out the cron job.

Unfortunately, the message is still thrown when starting and stopping postgresql, since the init script in postgresql-common is also running the pg_maintenance check.  Hopefully, a patch will fix.  This is something much more reasonable to live with then a cron job that doesn't work running every 5 hours.

Me, I like to bring up new systems with completely clean logs, and identify, fix any errors in those logs if running an existing system, and not run cron jobs that are not needed. ;>

Regards,
Jennifer
------=_Part_44234_16927605.1229805137837--