Jonathan Blitz writes:
I suppose I could do but I need to install PostgreSQL there and then copy
over the database.
Maybe I will give it a try.
I really think that is your best bet.
If for whatever reason that will not be an option perhaps you can just let
the process run over the weekend.. p
Most laptop drives are only 5,400 RPM which would make a transaction
like
you are describing likely take a while.
Not sure what my one is but it is new(ish).
If you're doing data intensive operations (like a big update which looks
like what you're doing) it will write many megabytes to
On Tue, 2006-05-30 at 16:04, Jonathan Blitz wrote:
> >
> > Most laptop drives are only 5,400 RPM which would make a transaction like
> > you are describing likely take a while.
>
> Not sure what my one is but it is new(ish).
>
> >
> > No desktop at home you could try it on?
> > I think the prob
>
> Most laptop drives are only 5,400 RPM which would make a transaction like
> you are describing likely take a while.
Not sure what my one is but it is new(ish).
>
> No desktop at home you could try it on?
> I think the problem with the laptop is likely it's drive.
I suppose I could do but I
Jonathan Blitz writes:
Nope. Didn't think it would make any difference.
May be worth a try.
I am using a laptop :).
Pentium 4 (not 4M) with 1GB of memory - 2 MHZ
Most laptop drives are only 5,400 RPM which would make a transaction like
you are describing likely take a while.
Must do it
>
>
> Could you do the updates in batches instead of trying to do them all at
> once?
Nope. Didn't think it would make any difference.
>
> Have you done a vacuum full on this table ever?
Many times
>
> What hardware?
> I have a dual CPU opteron with 4GB of RAM and 8 disks in RAID 10 (SATA).
Jonathan Blitz writes:
I just gave up in the end and left it with NULL as the default value.
Could you do the updates in batches instead of trying to do them all at
once?
Have you done a vacuum full on this table ever?
There were, in fact, over 2 million rows in the table rather than 1/4
> > So, I have tried to run the following command. The command never
finishes
> > (I gave up after about and hour and a half!).
>
> Did you ever find what was the problem?
> Perhaps you needed to run a vacuum full on the table?
Nope.
I just gave up in the end and left it with NULL as the default
Jonathan Blitz writes:
So, I have tried to run the following command. The command never finishes
(I gave up after about and hour and a half!).
Did you ever find what was the problem?
Perhaps you needed to run a vacuum full on the table?
---(end of broadcast)--
On Wed, May 17, 2006 at 03:19:26AM +0200, Jonathan Blitz wrote:
> I have a table of about 500,000 rows.
>
> I need to add a new column and populate it.
>
> So, I have tried to run the following command. The command never finishes (I
> gave up after about and hour and a half!).
If you install co
I have a table of about 500,000 rows.
I need to add a new column and populate it.
So, I have tried to run the following command. The command
never finishes (I gave up after about and hour and a half!).
Note that none of the columns have indexes.
Update mytable set new_column =
11 matches
Mail list logo
