From: Guido Barosio <gbarosio@gmail.com>
To: Dan The Man <bitsandbytes88@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: invalid length of startup packet
Date: Tue, 29 Nov 2005 21:49:56 +0000
Message-ID: <f7f6b4c70511291349p60dc46c1y942bada270e0250b@mail.gmail.com> (raw)
In-Reply-To: <BAY102-F29027D4E325B5677F3968DD14B0@phx.gbl>
References: <BAY102-F29027D4E325B5677F3968DD14B0@phx.gbl>
I can notice:
< % %2005-11-28 07:31:10 EST>LOG: database system was not properly shut
down; automatic recovery in progress
At a first sight, you didn't shut down the database as expected. (pg_ctl
stop -m smart/fast/immediate). Now I don't know if this is the root cause
for that message, but a clean stop, and start should show you if this is
related or not.
Just 2 cents, every little helps, best regards,
Guido Barosio
On 11/29/05, Dan The Man <bitsandbytes88@hotmail.com> wrote:
>
> Hi,
>
> I've been using postgresql v810 for a couple of weeks. I notice when I
> start it up I get 'invalid lenth of startup packet' On a database that I
> just initialized I get ' incomplete startup packet' after I first started
> it. This never happened that I can see in 8.0.3.
>
> Does any one know if that can be safely ignored?
>
> ~DjK
>
>
> < % %2005-11-28 07:31:10 EST>LOG: database system was interrupted at
> 2005-11-28 03:57:12 EST
> < % %2005-11-28 07:31:10 EST>LOG: checkpoint record is at 13/89BD9728
> < % %2005-11-28 07:31:10 EST>LOG: redo record is at 13/89BD9728; undo
> record is at 0/0; shutdown FALSE
> < % %2005-11-28 07:31:10 EST>LOG: next transaction ID: 81691647; next
> OID:
> 92997625
> < % %2005-11-28 07:31:10 EST>LOG: next MultiXactId: 1; next
> MultiXactOffset: 0
> < % %2005-11-28 07:31:10 EST>LOG: database system was not properly shut
> down; automatic recovery in progress
> < % %2005-11-28 07:31:10 EST>LOG: record with zero length at 13/89BD9778
> < % %2005-11-28 07:31:10 EST>LOG: redo is not required
> < % %2005-11-28 07:31:10 EST>LOG: database system is ready
> < % %2005-11-28 07:31:10 EST>LOG: transaction ID wrap limit is
> 1155432042,
> limited by database "dan_test_bum"
> <[unknown] %[unknown] %2005-11-28 09:03:07 EST>LOG: invalid length of
> startup packet
> < % %2005-11-28 09:43:37 EST>LOG: autovacuum: processing database
> "initial_db"
> < % %2005-11-28 09:53:37 EST>LOG: autovacuum: processing data
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
--
"Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: gbarosio@gmail.com, bitsandbytes88@hotmail.com
Subject: Re: invalid length of startup packet
In-Reply-To: <f7f6b4c70511291349p60dc46c1y942bada270e0250b@mail.gmail.com>
References: <BAY102-F29027D4E325B5677F3968DD14B0@phx.gbl> <f7f6b4c70511291349p60dc46c1y942bada270e0250b@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox