n you have below, you have 3 gigs worth of indexes. Do you
have that much data(in terms of rows)?
-Original Message-
From: Reece Hart [mailto:[EMAIL PROTECTED]
Sent: Wed 7/23/2003 1:07 PM
To: Guthrie, Jeremy
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; SF PostgreSQL
Subject:
On Wed, 2003-07-23 at 10:47, Guthrie, Jeremy wrote:
Have you checked the sizes of your indexes? You may need to rebuild them...
Multiply the relpages colum by 8192.
So, what does this tell me? I'm guessing that you're implying that I should expect 8192 keys per page, and that this therefor
Richard-
Thanks for the suggestions. I too had thought about the FK checks, even though the columns aren't getting updated.
I'm flabbergasted that the update is still running (~22 hours elapsed). By comparison, the database takes only 4 hours to recreate from backup! Something funny is happen
On Wednesday 23 July 2003 01:40, Reece Hart wrote:
> I'm trying to update a table but it's taking a very long time. I would
> appreciate any tips folks may have about ways to speed it up.
[snip]
> paprospect2 contains ~40M rows. The goal now is to migrate the data to
> the supertable-inherited colu
I'm trying to update a table but it's taking a very long time. I would appreciate any tips folks may have about ways to speed it up.
The table is paprospect2, as below:
\d paprospect2
Column | Type | Modifiers
-+-+-
