It's one of those "It's perfectly safe, as long as nothing goes wrong" types of things. It should work, but I'd certainly play on a test server first. And if something goes wrong in the right way, you might not even know it for a while. But generally, it's pretty common to do this one hackish thing with the catalogs. On Thu, Jan 27, 2011 at 1:25 PM, Jon Hoffman <jon@xxxxxxxxxxxxxx> wrote: > Hi, > I was able to do this without any issues, though I don't have any views. > - Jon > > On Thu, Jan 27, 2011 at 9:52 AM, Emi Lu <emilu@xxxxxxxxxxxxxxxxx> wrote: >> >> On 01/15/2011 04:22 PM, Jon Hoffman wrote: >>> >>> Hi, >>> >>> I found a post with some instructions for resizing without locking up >>> the table, but would like to get some re-assurance that this is the best >>> way: >>> >>> >>> http://sniptools.com/databases/resize-a-column-in-a-postgresql-table-without-changing-data >>> >>> How does that affect data storage and future updates on existing rows? >> >> I did not see any feedbacks about this topic. >> >> I need confirmation that it is safe to do this! Personally, I feel that it >> is specially useful when there are many view dependencies. Update from data >> dictionary, all views will be updated automatically, right? >> >> Thanks a lot! >> -- >> Lu Ying > > -- To understand recursion, one must first understand recursion. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
