Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: update from select
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: dev(at)kbsolutions(dot)ch
- Cc: pgsql-sql(at)postgresql(dot)org
- Subject: Re: update from select
- Date: Mon, 29 Oct 2007 14:42:57 -0400
- Message-id: <14485.1193683377@sss.pgh.pa.us> <text/plain>
<dev(at)kbsolutions(dot)ch> writes: > Hash Join (cost=10827.45..25950.05 rows=4906 width=1191) (actual > time=586.251..2852.691 rows=111306 loops=1) > ... > Total runtime: 633548.404 ms So you're worried about the wrong thing entirely. The query is taking less than 3 seconds, which may be reasonable considering it's producing 111000 join rows. The big problem is the other 630 seconds, which is evidently update overhead. I'm wondering if you have any triggers or foreign keys leading to or from this table. regards, tom lane
- References:
- update from select
- From: dev
- Re: update from select
- From: A. Kretschmer
- Re: update from select
- From: dev
- update from select
- Prev by Date: Re: update from select
- Next by Date: puzzled by SELECT INTO
- Previous by thread: Re: update from select
- Next by thread: Re: update from select
- Indexes: