Skip site navigation (1) Skip section navigation (2)

Re: slow cursor

From: "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: slow cursor
Date: 2006-04-21 03:45:57
Message-ID: 6992E470F12A444BB787B5C937B9D4DF0406AD88@ca-mail1.cis.local (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Yes..all of it is in one transaction as there is a window of record ids
that need to be processed in 1 transaction. Data inflow is very
voluminous appx 1 million every 15 minutes and the goal is to create
aggregate tables on the fly (the alternative is to use nightly

-----Original Message-----
From: Jim C. Nasby [mailto:jnasby(at)pervasive(dot)com] 
Sent: Thursday, April 20, 2006 7:36 PM
To: Sriram Dandapani
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] slow cursor

On Mon, Apr 17, 2006 at 07:07:54AM -0700, Sriram Dandapani wrote:
> I have a cursor that fetches 150K rows and updates or inserts a table
> with 150K rows.
> It takes several minutes for the process to complete (about 15
> The select by itself (without cursor) gets all rows in 15 seconds.
> Is there a way to optimize the cursor to fetch all records and speed
> the process. I still need to do the record by record processing

Not likely. Are you at least doing all this inside a transaction?
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461


pgsql-admin by date

Next:From: Benjamin KrajmalnikDate: 2006-04-21 03:52:30
Subject: Re: Howto: Using PITR recovery for standby replication
Previous:From: Jim C. NasbyDate: 2006-04-21 03:37:10
Subject: Re: track alter table history

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group