| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Larry Rosenman <ler(at)lerctr(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: help! |
| Date: | 2003-11-18 01:59:32 |
| Message-ID: | 3FB97D04.1080509@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Wait for confirmation from at least one other developer perhaps, buy you
can try this:
1. Set attisdropped to false for the attribute
2. Set the atttypid back to whatever the oid of the type of that column
is/was (Compare to an undropped similar column)
3. Use ALTER TABLE/SET NOT NULL on the column if it was originally NOT NULL
4. Set attstattarget to -1 to re-enable stat gathering
5. Rename the column (attname field) back to whatever it was.
6. Re set the default on the column
7. Done. (I think)
By the way, vacuuming doesn't necessarily have much to do with it -
updating rows does though. I'm not 100% sure what will happen exactly
when you follow the steps above (reversing what's in RemoveAttributeById).
Chris
Larry Rosenman wrote:
> I screwed up, and dropped a column when I shouldn't have.
>
> I have *not* vacuumed this DB yet.
>
> Is there any catalog mucking I can do to bring it back?
>
> LER
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-11-18 02:01:50 | Re: help! |
| Previous Message | Joshua D. Drake | 2003-11-18 01:58:20 | Re: Release cycle length |