On 2011-01-27, Emi Lu em...@encs.concordia.ca 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:
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
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 em...@encs.concordia.ca 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
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
On Thu, Jan 27, 2011 at 1:57 PM, Jon Hoffman j...@foursquare.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
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
On Thu, Jan 27, 2011 at 3:39 PM,
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
