X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4644ADB8B4 for ; Tue, 15 Nov 2005 12:42:32 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 51929-04-3 for ; Tue, 15 Nov 2005 16:42:28 +0000 (GMT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by svr1.postgresql.org (Postfix) with ESMTP id A97B8DB891 for ; Tue, 15 Nov 2005 12:42:27 -0400 (AST) Received: by xproxy.gmail.com with SMTP id h31so1517713wxd for ; Tue, 15 Nov 2005 08:42:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Vur3ipPqep0TXEcRMk6Nc/KIAI/DAR4irHT9962eNQPJLJypf4EtYLKng22dNTrEP/1C8BSfiTKuRW9So7RmSldO34VrHZ96giImuJae+mwKGbfzi54cSOne8ilL5c85/oekHVQwkdSZwKRk9YWScNZ90dpDoyT4RFjMJWMOSbk= Received: by 10.64.250.3 with SMTP id x3mr7416058qbh; Tue, 15 Nov 2005 08:42:27 -0800 (PST) Received: by 10.64.243.11 with HTTP; Tue, 15 Nov 2005 08:42:27 -0800 (PST) Message-ID: <38242de90511150842od57b6f6tbcde6a8867496a0f@mail.gmail.com> Date: Tue, 15 Nov 2005 09:42:27 -0700 From: Joshua Marsh To: pgsql-admin@postgresql.org Subject: Re: ERROR: could not read block In-Reply-To: <4379B89302000025000006E6@gwmta.wicourts.gov> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2794_31670456.1132072947343" References: <4379B89302000025000006E6@gwmta.wicourts.gov> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.333 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 1.333 X-Spam-Level: * X-Archive-Number: 200511/190 X-Sequence-Number: 19563 ------=_Part_2794_31670456.1132072947343 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 11/15/05, Kevin Grittner wrote: > > Could my issue be the same problem as this thread?: > > http://archives.postgresql.org/pgsql-bugs/2005-11/msg00114.php > > The references to "Invalid Argument" caught my eye. That thread > did start from a very different point, though. > > -Kevin It's possible. You said that the log file wasn't working, and you can reproduce the error, so the first thing I would do is solve the logging problem, then reproduce the error and see what the log says. I'm not familiar with pgsql on windows, but check to make sure you have logging turned on in the postgresql.conf file (this is on by default). Make sure you are logging to a file and directory that the pgsql service has permissions to write to. Does the windows system log give you any errors or warnings when pgsql starts? Perhaps it will describe why it's not logging. -Josh ------=_Part_2794_31670456.1132072947343 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 11/15/05, Kevin Grittner <Kevin.Grittner@wicourts.gov>= wrote:
Could my issue be the same problem as this thread?:

http://archives.= postgresql.org/pgsql-bugs/2005-11/msg00114.php

The references to= "Invalid Argument" caught my eye.  That thread
did start from a very different point, though.

-Kevin

It's possible.  You said that the log file wasn't working, and you can reproduce the error, so the first thing I would do is solve the logging problem, then reproduce the error and see what the log says. 

I'm not familiar with pgsql on windows, but check to make sure you have logging turned on in the postgresql.conf file (this is on by default). = ; Make sure you are logging to a file and directory that the pgsql service has permissions to write to.

Does the windows system log give you any errors or warnings when pgsql star= ts? Perhaps it will describe why it's not logging.

-Josh 

------=_Part_2794_31670456.1132072947343--