From: Scott Marlowe <scott.marlowe@gmail.com>
To: Mark Steben <msteben@autorevenue.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Mass updates on a large table
Date: Fri, 10 Aug 2007 14:41:16 -0500
Message-ID: <dcc563d10708101241q16bf96et6b4dc2347555f70e@mail.gmail.com> (raw)
In-Reply-To: <009b01c7db7f$a5c0e440$b501a8c0@D1RPQZB1>
References: <dcc563d10708101057l7dd53571w39a333988a12c84@mail.gmail.com>
<009b01c7db7f$a5c0e440$b501a8c0@D1RPQZB1>
On 8/10/07, Mark Steben <msteben@autorevenue.com> wrote:
>
>
>
>
> Hi Scott, thanks for the response.
> 4. The business reason for the update: we are replacing within a
> query a
> COALESCE function that gave us the most recent date between 3 dates. We
> Are instead doing the COALESCE as part of a new update trigger, populating
> the New date fields with the most recent dates and referencing the new dates
So this is a one time data migration. OK, then I'm no as worried
about the business case being a bit crazy.
> 5. We are planning an upgrade to 8.2.4 in the near future – hopefully
> in a couple months.
Cool. Start testing now. You'd be surprised how many test cases
you'll find where your laptop running 8.2 will outrun your server
running 7.x...
Nothing too out of the ordinary in your schema, but those
multi-dimensional arrays might be a bit expensive, especially for
updates.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, msteben@autorevenue.com
Subject: Re: Mass updates on a large table
In-Reply-To: <dcc563d10708101241q16bf96et6b4dc2347555f70e@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox