Andrew Sullivan wrote:
> On Fri, Aug 24, 2007 at 10:06:56AM -0400, Feng Chen wrote:
> > VERSION = PostgreSQL 8.1.2
>
> You know that the project doesn't put out maintenance releases for
> the fun of it, right? The latest is 8.1.9 in that series. You need
> to upgrade.
We moved the "you should u
"Tom Lane" <[EMAIL PROTECTED]> writes:
> It's still pointless; a checksum does nothing to prevent data
> corruption. The error report might be slightly more obvious to a novice
> but it doesn't bring your data back.
Well if it's a single bit error from bad memory or a torn page from having
full
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> Remember that the xmin/xmax fields are basically the first thing we can
>> check with any degree of strictness when examining a tuple. This means that
>> if a page is partially clobbered, but not in a way that set
Yes, most of the time PostgreSQL only complains about missing pg_clog/
files then complains about invalid page headers. The "could not create
... File exists" message was only seen a couple of times.
I don't have a system that exhibits this problem right now. I can check
the XID counter when it h
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Remember that the xmin/xmax fields are basically the first thing we can
> check with any degree of strictness when examining a tuple. This means that
> if a page is partially clobbered, but not in a way that sets off the
> invalid-page-header checks, then
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> Feng Chen wrote:
>> VERSION = PostgreSQL 8.1.2
> this could be
> http://archives.postgresql.org/pgsql-committers/2006-01/msg00287.php
Note, however, that that only explains the "could not create ... File
exists" complaint, which is hardly the main
Thanks for the replies! I guess it's time for 8.1.9 then. Will keep you
informed afterwards!
-Original Message-
From: Andrew Sullivan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 10:14 AM
To: Andrew Sullivan
Cc: Feng Chen; Alvaro Herrera; Gregory Stark; Marc Schablewski;
Decibe
On Fri, Aug 24, 2007 at 10:11:06AM -0400, Andrew Sullivan wrote:
> On Fri, Aug 24, 2007 at 10:06:56AM -0400, Feng Chen wrote:
> > VERSION = PostgreSQL 8.1.2
>
> You know that the project doesn't put out maintenance releases for
> the fun of it, right? The latest is 8.1.9 in that series. You need
Feng Chen wrote:
> VERSION = PostgreSQL 8.1.2
this could be
http://archives.postgresql.org/pgsql-committers/2006-01/msg00287.php
which is fixed in 8.1.3 and later - so you really should look into
upgrading to 8.1.9 as soon as possible ,,,
Stefan
---(end of broadcast)---
On Fri, Aug 24, 2007 at 10:06:56AM -0400, Feng Chen wrote:
> VERSION = PostgreSQL 8.1.2
You know that the project doesn't put out maintenance releases for
the fun of it, right? The latest is 8.1.9 in that series. You need
to upgrade.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Unfortunately refo
VERSION = PostgreSQL 8.1.2
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 10:02 AM
To: Feng Chen
Cc: Gregory Stark; Marc Schablewski; Decibel!; pgsql-bugs@postgresql.org
Subject: [SPAM] Re: [BUGS] BUG #3484: Missing pg_clog file / corrupt i
Feng Chen wrote:
> We also have the same exact problem - every 5 to 10 days when the data
> get to some size, PostgreSQL complains about missing pg_clog files, and
> invalid page headers during either vacuum or reindex operations.
What PG version is this?
> 2007-08-13T10:12:15+00:00 ERROR: coul
Feng Chen wrote:
> We also have the same exact problem - every 5 to 10 days when the data
> get to some size, PostgreSQL complains about missing pg_clog files, and
> invalid page headers during either vacuum or reindex operations.
>
> The problem happens on different customer sites with Linux 2.6.
On Fri, Aug 24, 2007 at 09:19:49AM -0400, Feng Chen wrote:
> The problem happens on different customer sites with Linux 2.6.11.
Well, at kernel.org in the changelog for 2.6.12, I see this:
[PATCH] PCI: don't override drv->shutdown unconditionally
There are many drivers that have been
We also have the same exact problem - every 5 to 10 days when the data
get to some size, PostgreSQL complains about missing pg_clog files, and
invalid page headers during either vacuum or reindex operations.
The problem happens on different customer sites with Linux 2.6.11.
There is one particula
15 matches
Mail list logo
