| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: database corruption |
| Date: | 2003-08-30 22:00:31 |
| Message-ID: | 3112.1062280831@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Fortunately this was his own development database he was messing with,
> but it was an interesting exercise none-the-less. Maybe this reinforces
> the need to have a command for enabling/disabling triggers.
No, it reinforces the cardinal rule about not experimenting with system
catalog alterations in databases you care about. If he'd done his
experimentation in a scratch database, he'd not have been in trouble.
Perhaps we need some documentation about What Not To Do As Superuser.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2003-08-30 22:09:40 | Re: ALTER TABLE ... TO ... to change related names |
| Previous Message | Tom Lane | 2003-08-30 21:50:59 | Re: [HACKERS] What goes into the security doc? |