> Following is one of the update query and it's explain plan which takes
> about 6 mins to execute. I am trying to find a way to execute it faster.
> The functions used in the update statement are if then else test and
> then return one value or the other.
>
On 1/31/07, Sidar López Cruz <[EMAIL PROTECTED]> wrote:
Executing these query take:
Query returned successfully: 290 rows affected, 2542387 ms execution time.
I think that's too many time
I would post the plans that you are getting, otherwise just mentioning the
execution time is not very hel
Following is one of the update query and it's explain plan which takes about 6
mins to execute. I am trying to find a way to execute it faster. The functions
used in the update statement are if then else test and then return one value or
the other.
===
From: Ted Allen <[EMAIL PROTECTED]>
To: Sidar López Cruz <[EMAIL PROTECTED]>
CC: pgsql-performance@postgresql.org, [EMAIL PROTECTED]
Subject: Re: [PERFORM] Very slow queries
Date: Wed, 31 Jan 2007 09:32:43 -0500
How many rows were delete last time you ran the query?
Chad's query looks good but
Gregory Stark <[EMAIL PROTECTED]> writes:
> On the other there are some common situations where you could see
> atypical increases. Consider joining a bunch of small tables to
> generate a large result set. The small tables are probably all in
> memory and the result set may only have a small numbe
How many rows were delete last time you ran the query?
I never delete any rows, the tables was inserted with copy command, then I
create index and I need to delete these records on ceroriesgo.salarios to
create the foreign key restriction on it.
Chad's query looks good but here is another
I strongly encourage anyone who is interested in the general external
sorting problem peruse Jim Gray's site:
http://research.microsoft.com/barc/SortBenchmark/
Ron Peacetree
At 08:24 AM 1/31/2007, Gregory Stark wrote:
Tom Lane <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> w
How many rows were delete last time you ran the query?
Chad's query looks good but here is another variation that may help.
Delete From ceroriesgo.salarios Where numero_patrono In (Select
ceroriesgo.salarios.numero_patrono From ceroriesgo.salarios Left Join
ceroriesgo.patronos Using (numero_p
From: "Chad Wagner" <[EMAIL PROTECTED]>
To: "Sidar López Cruz" <[EMAIL PROTECTED]>
CC: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Very slow queries
Date: Tue, 30 Jan 2007 17:37:17 -0500
On 1/30/07, Sidar López Cruz <[EMAIL PROTECTED]> wrote:
query: Delete From ceroriesgo.salari
Tom Lane <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Gregory Stark wrote:
> >> (Incidentally I'm not sure where 2-5x comes from. It's entirely dependant
> >> on
> >> your data distribution. It's not hard to come up with distributions where
> >> it's
> >> 1000x as
10 matches
Mail list logo
