Re: [BUGS] BUG #1745: Unable to delete data from the database

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:     1745 <br />Logged by:          K.G.Sivaraman <br />Email address:      ksivaram@ssd.usa.alcatel.com <br
/>PostgreSQLversion: 8.0 <br />Operating system:   Solaris <br />Description:        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
parametersand both are indexed), it returns success. <br />But when queried again, then the deleted name appeared. <br
/>Whenwe analysed the problem, the basic delete <br />command itself not working. <br />Normally DELETE command will
returnthe 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
request0/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 ---
writeerror may be <br />permanent. <p>But when I add a new record, it is getting added and <br />I am able to delete
thenewly 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
/>      choose an index scan if your joining column's datatypes do not <br />       match</blockquote><pre>-- 
 
K.G.Sivaraman, Axes Technologies (I) Pvt Ltd

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