From: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL on XFS experiences? |
Date: | 2004-02-26 20:09:21 |
Message-ID: | 1077826161.28192.1.camel@heat |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2004-02-26 at 11:46, Holger Marzen wrote:
> On Thu, 26 Feb 2004, Jeffrey W. Baker wrote:
>
> > We are using PostgreSQL with the database and xlogs on (separate) XFS
> > volumes under Linux 2.4.25. We are simply curious to hear your
> > experiences with this combination, if you are using it. In only two
> > days of heavy activity, we've already been able to corrupt one
> > database. We've also seen XFS panic because of inconsistent in-memory
> > metadata. Frankly we don't have the highest confidence.
>
> I am afraid that xfs in that kernel or your hardware is buggy (probably
> RAM). A 24h run of memtest86 wouldn't be bad.
>
> Since PostgreSQL uses the operating system's calls for file operations
> as any other program does, it's most probably no PostgreSQL issue.
I don't see why not. PostgreSQL could easily have a bug that swaps a
buffer somewhere, resulting in a corrupt table. That we see this only
on the INSERT path and not the COMMIT path also seems to point towards
Pg.
Anyway, you didn't mention XFS. Do you have experience using it beneath
Postgres?
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-02-26 20:10:37 | Re: key = currval('tab_key_seq') choses SEQSCAN?! |
Previous Message | Holger Marzen | 2004-02-26 19:46:22 | Re: PostgreSQL on XFS experiences? |