Hi,
I'm a noob who failed to properly sanitize incoming data from the
front end. As a result, a poor hapless user managed to smuggle in a
malicious UPDATE statement that corrupted every single record in a
7+ table. Only 3 fields were corrupted and of those only one is
vital. But it's REALLY
Thanks for the replies.
Tom Lane wrote:
> This being 8.1, if you haven't turned on autovacuum there is some chance
> of that.
Unfortunately, autovacuum was on. I don't recall ever turning it on,
but this database is over two years old; it's possible that I blindly
followed advice from pgAdmin or
approach won't
work, as autovacuum was on at the time of corruption. However, the
files in the data directory are quite large -- many times larger than
a pg_dump. The database sees such a small amount of traffic that it's
possible that even vacuum decided not to bother reclaiming the unus
ned my lesson, I've set up a utility to run
pg_dump each day. After I've taken a break, I'll look into a
reasonabe set-up for file system backups with point-in-time recovery.
But really, what are the chances anything like this will ever happen
again? ;-)
-Gus
On Mon, Jun 15, 200
