| From: | Stephen Davies <scldad(at)sdc(dot)com(dot)au> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | records zapped to null |
| Date: | 2001-03-27 03:33:53 |
| Message-ID: | 200103270333.NAA29055@mustang.sdc.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello again.
I have just had to restore a database from backup because the majority
of records in one table had "magically" become null.
Last Friday morning there were some 700 valid rows in the table but yesterday
all but 42 had become totally null.
Restoring from Thursday night's backup repaired things so I am
wondering what could have happened in between to cause this strange
phenomenon.
Cheers and thanks,
Stephen Davies
========================================================================
Stephen Davies Consulting scldad(at)sdc(dot)com(dot)au
Adelaide, South Australia. Voice: 08-8177 1595
Computing & Network solutions. Fax: 08-8177 0133
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zak McGregor | 2001-03-27 03:36:14 | Re: How to auto create a unique key for each newly added record? |
| Previous Message | Zak McGregor | 2001-03-27 03:20:50 | Views, indices and pg_dump |