| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Jon Hoffman <jon(at)foursquare(dot)com> |
| Cc: | emilu(at)encs(dot)concordia(dot)ca, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: resizing a varchar column on 8.3.8 |
| Date: | 2011-01-27 21:57:34 |
| Message-ID: | AANLkTinC3MVefJPrHWiE4A2=sjc8kdUjmb1vN7+CUJQS@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 27, 2011 at 1:57 PM, Jon Hoffman <jon(at)foursquare(dot)com> wrote:
> This was originally discussed on this list
> here: http://postgresql.1045698.n5.nabble.com/Smartest-way-to-resize-a-column-td1915892.html
> Tom Lane suggested doing the resize in a BEGIN block at least to verify that
> "\d tablename" reflects the catalog update.
> - Jon
Good point. Best practices are to do all DDL in a transaction if
possible. But a lot of folks come from databases that do stupid and
unpredictable things when you try to do DDL in a transaction (ok,
that's basically damned near all of them except a couple of odd
rarities like informix)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lawrence Cohan | 2011-01-27 22:02:39 | Re: Adding ddl audit trigger |
| Previous Message | Scott Marlowe | 2011-01-27 20:57:53 | Re: Adding ddl audit trigger |