Hello all,
I have a table consisting of about 450.000 rows
with a unique primary key char(9)
kundennummer CHAR(9) unique primary key
... some fields...
miano CHAR(6)
Today someone issued an
UPDATE table SET miano='071002' WHERE kundennummer='071002883';
and managed to UPDATE all the 450.000 rows, updating
the miano to the value '071002' by issuing this command.
The update is generated through a web-based intranet-solution,
unfortunately I didn't have a postgresql-logfile for this, but
I can see from the webserver logfile, which scripts was run
at the particular time.
For me it's almost 99.9 % sure, that it's no error in the
perl-program. There is only one command issuing exactly
SQL("UPDATE $table SET $daten WHERE kundennummer='$kundennummer';");
where $table is the table-variable
$daten is what is to be set
$kundennummer is the client-number, which is checked before to match exactly
9 digits.
Could there be any postgresql-server-side explanation for this phenomenom ?
Perhaps
anything about corrupted indexes, or anything?
--
Mit freundlichem Gruß
Henrik Steffen
Geschäftsführer
top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com Tel. +49 4141 991230
mail: steffen@topconcepts.com Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
Ihr SMS-Gateway: JETZT NEU unter: http://sms.city-map.de
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------
