| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Diana Nemirovsky <diana(at)marinconsulting(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: ADD COLUMN damage control |
| Date: | 2005-07-18 13:29:10 |
| Message-ID: | 2545.1121693350@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Diana Nemirovsky <diana(at)marinconsulting(dot)com> writes:
> Then site-wide, things all broke. I deleted (cascade) the trigger, but what
> was breaking was across all tables, and not just on the tables touched by
> my trigger. Queries that used to work fine no longer do. Not having any
> other logical explanation, I looked up the VACUUM command, and tried that
> on each table. Same result. Things are broken all over the place.
No one can possibly help you with such a vague problem report. Don't
say "broken", show us a few examples of specific queries and the exact
error messages you get.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-18 13:38:02 | Re: Problem with starting Postgres |
| Previous Message | Reinhard Hnat | 2005-07-18 09:49:30 | Problem with starting Postgres |