X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 0D32C9FA68D for ; Fri, 21 Jul 2006 18:18:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 76712-05 for ; Fri, 21 Jul 2006 18:18:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3B12F9FA43C for ; Fri, 21 Jul 2006 18:18:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6LLI3f0007985; Fri, 21 Jul 2006 17:18:03 -0400 (EDT) To: "Chris Hoover" cc: "pgsql-admin@postgresql.org" Subject: Re: log entries after pitr recovery In-reply-to: <1d219a6f0607211242n7da791a0vf2d165546ec60cc4@mail.gmail.com> References: <1d219a6f0607211242n7da791a0vf2d165546ec60cc4@mail.gmail.com> Comments: In-reply-to "Chris Hoover" message dated "Fri, 21 Jul 2006 15:42:15 -0400" Date: Fri, 21 Jul 2006 17:18:03 -0400 Message-ID: <7984.1153516683@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.068 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/176 X-Sequence-Number: 22422 "Chris Hoover" writes: > ,11962,,2006-07-13 16:11:16.281 EDT,,360,,,,LOG: invalid server process ID > -1 See 8.1.4 fix: 2006-03-30 17:11 tgl * src/backend/storage/smgr/smgr.c (REL8_1_STABLE): Suppress attempts to report dropped tables to the stats collector from a startup or recovery process. Since such a process isn't a real backend, pgstat.c gets confused. This accounts for recent reports of strange "invalid server process ID -1" log messages during crash recovery. There isn't any point in attempting to make the report, since we'll discard stats in such scenarios anyhow. regards, tom lane