Eric Ridge <ebr@tcdi.com> writes:Using PG 7.3.x, how stupid is this: UPDATE pg_attribute SET atttypmod=<new size + 4> WHERE ....;
It'll work okay for a varchar column (not char) at least as far as the table itself is concerned. I think there are some issues for views referencing the column, possibly also indexes.
We haven't discovered any issues. We do in fact have views sitting infront of the these tables (w/ a bunch of update/insert rules too!) and indexes. All seems to be well.
Can you speculate on what the issue would be? Perceived data loss (ie, values that exceed the original size are truncated)? Inability to update? Index scans not returning rows? Or would it be some kind of fail-fast ERROR:?
eric
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
