Hello All,
I've looked through the docs, but I'm unable to find complete answers to my
questions, so thanks in advance if you can lend any expertise.
Here's the situation I'm in (always a good opener, right? :) ):
We've got a postgres database with *a lot* of data in one table. On the
order of
Tim,
Commando. I like it. Thanks a ton for that suggestion. I'd still like to
hear if anyone has a good way to estimate the performance of these
operations, but I'll explore what it would mean to do exactly that.
John: thankfully this is a table without any fks in, although it is indexed
to he
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 wrote:
> On 03/12/12 5:01 PM
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 wrote:
> John,
>
> Thanks, I'll clarify my language around that.
>
> Still hoping
rdware, take all the advice offered here,
and just see how it performs.
Thanks to everyone for the feedback,
Carson
On Tue, Mar 13, 2012 at 6:32 PM, John R Pierce wrote:
> On 03/13/12 6:10 PM, Carson Gross wrote:
>
>> As a follow up, is the upgrade from integer to bigint vio
onable guess as to the inserts per second postgres
is capable of these days on middle-of-the-road hardware? Any order of
magnitude would be fine: 10, 100, 1000, 10,000.
Thank you all for your patience,
Carson
On Tue, Mar 13, 2012 at 8:24 PM, Carson Gross wrote:
> Got it.
>
> Thank you,
14 at 00:24 -0700, John R Pierce wrote:
> > On 03/13/12 8:41 PM, Carson Gross wrote:
> > > Does anyone have a reasonable guess as to the inserts per second
> > > postgres is capable of these days on middle-of-the-road hardware? Any
> > > order of magnitude would be
I've got a pretty big database (~30 gigs) and when I do a pg_dump, it ends
up only being 2 gigs.
The database consists mainly of one very large table (w/ a few varchar
columns) which, according to pg_relation_size() is 10 gigs
and pg_total_relation_size() is 26 gigs (we need to drop some indexes
t
: I'm downloading it now to check.
Thanks for the replies,
Carson
On Thu, Mar 29, 2012 at 12:11 AM, John R Pierce wrote:
> On 03/28/12 10:32 PM, Carson Gross wrote:
>
>> I've got a pretty big database (~30 gigs) and when I do a pg_dump, it
>> ends up only being 2 gigs.
