Re: Performance: Perl-DBI vs. PG Stored Procedures - Mailing list pgsql-general

From Alex Avriette
Subject Re: Performance: Perl-DBI vs. PG Stored Procedures
Date
Msg-id 32BAF2A2B169D411A081009027464529025DB397@ATD-NT5
Whole thread Raw
In response to Performance: Perl-DBI vs. PG Stored Procedures  (David Link <dlink@soundscan.com>)
List pgsql-general
Yes. The PL/SQL programs will be faster since theyre stored in postgres.

Doing things like nested selects, however, will be faster in perl with
arrays/hashes than they would be in sql. you might also consider dropping
any indexes you have before inserting and then re-creating them. this is
provided, of course, you only have one concurrent user.

alex

-----Original Message-----
From: David Link [mailto:dlink@soundscan.com]
Sent: Tuesday, November 20, 2001 11:10 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Performance: Perl-DBI vs. PG Stored Procedures


Hi,

Could there be performance gains by using PG stored procedures rather
than using generic Perl DBI programs?

Namely for a task that loops thru a cursor of several 50,000 rows and
does UPDATES or INSERTS back into that same table.  It is takes hours.

Thanks, David

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

pgsql-general by date:

Previous
From: RoBSD
Date:
Subject: NOTICE: (transaction aborted): queries ignored until END
Next
From: Bruce Momjian
Date:
Subject: Re: dropdb to a remote host