Re: Performance: Perl-DBI vs. PG Stored Procedures

From: Alex Avriette <a_avriette(at)acs(dot)org>
To: "'David Link'" <dlink(at)soundscan(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Performance: Perl-DBI vs. PG Stored Procedures
Date: 2001-11-20 18:09:27
Message-ID: 32BAF2A2B169D411A081009027464529025DB397@ATD-NT5
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)soundscan(dot)com]
Sent: Tuesday, November 20, 2001 11:10 AM
To: pgsql-general(at)postgresql(dot)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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Avriette 2001-11-20 18:15:15 Re: dropdb to a remote host
Previous Message wsheldah 2001-11-20 17:54:07 Re: A newbie's opinion - postgres NEEDS a Windows