BUG #1745: Unable to delete data from the database

Started by K.G.Sivaramanover 20 years ago3 messages
#1K.G.Sivaraman
ksivaram@ssd.usa.alcatel.com

The following bug has been logged online:

Bug reference: 1745
Logged by: K.G.Sivaraman
Email address: ksivaram@ssd.usa.alcatel.com
PostgreSQL version: 8.0
Operating system: Solaris
Description: Unable to delete data from the database
Details:

When try to delete the existing name in the database (having ID and Name as
the table parameters and both are indexed), it returns success.
But when queried again, then the deleted name appeared.
When we analysed the problem, the basic delete
command itself not working.
Normally DELETE command will return the number of records deleted (ex)
DELETE 1 for 1 record.
But now, it returns DELETE 0, even though the
record is there and it is not got deleted.

The error in the log file is as follows :

ERROR : xlog flush request 0/D17B00 is not satisfied --- flushed only to
0/C31ED0
CONTEXT : writing block 0 of relation 17231/17232/17249
WARNING : could not write block 0 of 17231/17232/17249
DETAIL : Multiple failures --- write error may be
permanent.

But when I add a new record, it is getting added and
I am able to delete the newly added record.

Why this error coming ?. Can some one can help ?.

#2Sivaraman K.G
Ganapathy.Sivaraman@alcatel.com
In reply to: K.G.Sivaraman (#1)
Re: [BUGS] BUG #1745: Unable to delete data from the database

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<p>Since I didn't get any response, I am just posting in pgsql-hackers.
<br>Can any one help ?.
<p>Thanks
<br>Siva
<p>> "K.G.Sivaraman" wrote:
<blockquote TYPE=CITE>The following bug has been logged online:
<p>Bug reference:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1745
<br>Logged by:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; K.G.Sivaraman
<br>Email address:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ksivaram@ssd.usa.alcatel.com
<br>PostgreSQL version: 8.0
<br>Operating system:&nbsp;&nbsp; Solaris
<br>Description:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unable to delete
data from the database
<br>Details:
<p>When try to delete the existing name in the database (having ID and
Name as
<br>the table parameters and both are indexed), it returns success.
<br>But when queried again, then the deleted name appeared.
<br>When we analysed the problem, the basic delete
<br>command itself not working.
<br>Normally DELETE command will return the number of records deleted (ex)
<br>DELETE 1 for 1 record.
<br>But now, it returns DELETE 0, even though the
<br>record is there and it is not got deleted.
<p>The error in the log file is as follows :
<p>ERROR : xlog flush request 0/D17B00 is not satisfied --- flushed only
to
<br>0/C31ED0
<br>CONTEXT : writing block 0 of relation 17231/17232/17249
<br>WARNING : could not write block 0 of 17231/17232/17249
<br>DETAIL : Multiple failures --- write error may be
<br>permanent.
<p>But when I add a new record, it is getting added and
<br>I am able to delete the newly added record.
<p>Why this error coming ?. Can some one can help ?.
<p>---------------------------(end of broadcast)---------------------------
<br>TIP 9: In versions below 8.0, the planner will ignore your desire to
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; choose an index scan if your joining
column's datatypes do not
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; match</blockquote>

<pre>--&nbsp;
K.G.Sivaraman, Axes Technologies (I) Pvt Ltd

"The only SERVICE to be done for our lower classes is to give them&nbsp;
EDUCATION, to develop their lost individuality" - Swami Vivekananda</pre>
&nbsp;</html>

#3Dennis Bjorklund
db@zigo.dhs.org
In reply to: Sivaraman K.G (#2)
Re: [BUGS] BUG #1745: Unable to delete data from the

On Sun, 10 Jul 2005, Sivaraman K.G wrote:

The error in the log file is as follows :

ERROR : xlog flush request 0/D17B00 is not satisfied ---
flushed only to
0/C31ED0
CONTEXT : writing block 0 of relation 17231/17232/17249
WARNING : could not write block 0 of 17231/17232/17249
DETAIL : Multiple failures --- write error may be
permanent.

Check your kernel log for disk errors. It could very well be that your
disk is about to die (or already have).

--
/Dennis Bj�rklund