Tom-
Thanks for the quick response. More details are inline.
-mike
On Thu, 01 Jan 2004 23:06:11 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Mike Glover <[EMAIL PROTECTED]> writes:
> AFAICS these plans are identical, and therefore the difference in
> runtime must be ascribed to the time spe
Mike Glover <[EMAIL PROTECTED]> writes:
> I want to run the following query, but it takes a *very* long time.
> Like this:
> bookshelf=> explain analyze update summary set price_min=0,
> availability=2, condition=9 where isbn = inventory.isbn and price_min =
> inventory.price;
I have these two tables:
Table "de.summary"
Column|Type | Modifiers
--+-+---
isbn | character varying(10) | not null
source | character varying(20) | not null
Happy new year!
When performing
"pg_restore -L list --disable-triggers -d db1 -v my_archive"
, my hard disk for Linux box (with 96MB RAM) becomes
extremely busy.
One example is that it takes more than 5 miniutes to restore
for a table from 7800 rows. Each row has less than 117
bytes in length
