Re: Corrupted sequences

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Francisco Reyes <lists(at)natserv(dot)com>
Cc: pgsql General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Corrupted sequences
Date: 2003-03-14 20:18:19
Message-ID: Pine.LNX.4.33.0303141317340.23951-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 14 Mar 2003, Francisco Reyes wrote:

> Got 2 corrupted sequences, that I have discovered so far, and fixed them
> with 'setval'. Is there a way to check all sequences in a database?
> Something simmilar to reindex but for sequences?
>
>
> Running 7.2.4 (at my ISP so don't have a choice there..)

You need to demand that your service providers test their hardware. When
things randomly get corrupted in Postgresql it is about 95% of the time or
more that you have either a bad disk or bad memory. Postgresql is good,
but it can't overcome broken hardware.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Reyes 2003-03-14 20:21:21 Re: Corrupted sequences
Previous Message scott.marlowe 2003-03-14 20:17:17 Re: The folding of unquoted names to lower case in PostgreSQL