From: | Ron Peterson <rpeterso(at)mtholyoke(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: alter column appears to work, but doesn't? |
Date: | 2011-09-05 20:00:15 |
Message-ID: | 20110905200015.GB3061@mtholyoke.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2011-09-05_15:03:00-0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Ron Peterson <rpeterso(at)mtholyoke(dot)edu> writes:
> > I just updated a table to have a larger column size as follows.
>
> > alter table attributes_log alter column attribute_name type varchar(48);
>
> How come this refers to "attributes_log" while your failing command is
> an insert into "attributes"?
That was a typo, sorry. Did do the same thing on original table. I did
the same thing to attributes_log because I have rules that log data
there from my original table on insert/update/delete.
I just dropped my logging rules, stopped the database and restarted it,
put my rules back in place, and now it works. Not sure why. Cached
query plan?
--
Ron Peterson
Network & Systems Administrator
Mount Holyoke College
http://www.mtholyoke.edu/~rpeterso
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Hodgson | 2011-09-05 20:00:45 | Re: warm standby - apply wal archives |
Previous Message | Tom Lane | 2011-09-05 19:10:55 | Re: [GENERAL] pg_upgrade problem |