As a follow up, is the upgrade from integer to bigint violent? I assume so: it has to physically resize the column on disk, right?
Thanks, Carson On Tue, Mar 13, 2012 at 9:43 AM, Carson Gross <carsongr...@gmail.com> wrote: > John, > > Thanks, I'll clarify my language around that. > > Still hoping that there is a way to get a rough estimate of how long > converting an integer column to a bigint will take. Not possible? > > Thanks guys, > Carson > > > On Mon, Mar 12, 2012 at 6:13 PM, John R Pierce <pie...@hogranch.com>wrote: > >> On 03/12/12 5:01 PM, Carson Gross wrote: >> >>> >>> We are also considering sharding the table and maybe the right thing is >>> to simply fix it when we do the sharding. >>> >> >> postgres generally calls that partitioning... Sharding usually means >> splitting data across multiple servers. >> >> >> >> >> -- >> john r pierce N 37, W 122 >> santa cruz ca mid-left coast >> >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general> >> > >
