From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Peterson <stevep-hv@zpfe.com>
Cc: me@alternize.com
Cc: pgsql-performance@postgresql.org
Subject: Re: UPDATE becomes mired / win32
Date: Thu, 05 Oct 2006 09:19:24 -0400
Message-ID: <12200.1160054364@sss.pgh.pa.us> (raw)
In-Reply-To: <6.2.3.4.0.20061005000508.04bb03d8@localhost>
References: <6.2.3.4.0.20061004094635.03c114a8@localhost>
<0d3301c6e7e0$ce71c190$6501a8c0@iwing>
<6.2.3.4.0.20061005000508.04bb03d8@localhost>
Steve Peterson <stevep-hv@zpfe.com> writes:
> The behavior also persists across a dump/reload of the table into a
> new install on a different machine. IIRC dump/reload rebuilds
> indexes from scratch.
Hm. There must be something you're not telling us that accounts for
the difference between the original table and the copied version ---
foreign keys linking from other tables, perhaps?
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, stevep-hv@zpfe.com, me@alternize.com
Subject: Re: UPDATE becomes mired / win32
In-Reply-To: <12200.1160054364@sss.pgh.pa.us>
* 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