;Keith C. Perry" <[EMAIL PROTECTED]>
To: "Andrew Hall" <[EMAIL PROTECTED]>
Cc: "Alban Hertroys" <[EMAIL PROTECTED]>; "Marco Colombo"
<[EMAIL PROTECTED]>;
Sent: Saturday, February 26, 2005 6:02 AM
Subject: Re: [GENERAL] Lost rows/data corr
c.).
- Original Message -
From: "Michael Fuhr" <[EMAIL PROTECTED]>
To: "Andrew Hall" <[EMAIL PROTECTED]>
Cc: "Scott Marlowe" <[EMAIL PROTECTED]>; "Alban Hertroys"
<[EMAIL PROTECTED]>; "Marco Colombo" <[EMAIL PROTEC
I was wondering if this problem had ever shown up on a machine that
HADN'T lost power abrubtly or not. IFF the only machines that
experience corruption have lost power beforehand sometime, then I would
look towards either the drives, controller or file system or somewhere
in there.
I can't be sure
Do you happen to have the same type disks in all these systems? That could
point to a disk cache "problem" (f.e. the disks lying about having written
data from the cache to disk).
Or do you use the same disk parameters on all these machines? Have you
tried using the disks w/o write caching and/
I know this is a silly question, but when you write 'We do nothing with
any indexes' do you mean indeces are never, _never_ touched (I mean
explicitly, as in drop/create index), i.e. they are created at schema
creation time and then left alone? Just to make sure...
Hi and thanks for your feedback,
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Andrew Hall" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, February 15, 2005 3:25 PM
Subject: Re: [GENERAL] Lost rows/data corruption?
"Andrew Hall" <[EMAIL PROTECTED]> writes:
Here
nging the way the data is stored)
- the version of Jetty (servlet engine)
- the DB pool manager and PG JDBC driver versions
- the version of PG (tried two or three back from the latest)
- various vacuum regimes
- Original Message -
From: "Marco Colombo" <[EMAIL PROTECTED]>
To
It sounds like a mess, all right. Do you have a procedure to follow to
replicate this havoc? Are you sure there's not a hardware problem
underlying it all?
regards, tom lane
We haven't been able to isolate what causes it but it's unlikely to be
hardware as it happens on quite a few of our custom
rigger AFTER DELETE ON user_session FOR EACH ROW EXECUTE
PRO
CEDURE delsessionusagefunc()
I'm most concerned that a primary constraint is being actively violated, and
I don't understand how this is possible.
Any help appreciated.
- Original Message -
From: "Tom Lane"
Hello,
We have a long running DB application using PG7.4.6. We do a VACUUM FULL
every night and a normal 'maintenance' VACUUM every hour. We do nothing with
any indexes. Every now and then we get errors from the database whereby an
update will fail on a table saying that there is duplicate viola
Hello,
We have a long running DB application using PG7.4.6. We do a VACUUM FULL
every night and a normal 'maintenance' VACUUM every hour. We do nothing with
any indexes. Every now and then we get errors from the database whereby an
update will fail on a table saying that there is duplicate violatio
Hello,
We are using a number of stored procedures that are called often from our
client programs. I include one here as an example. The problem we are seeing
is that when executing some of these that deal with a large number of
records, they begin execution and never return. The process handling t
12 matches
Mail list logo
