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

Re: PosgreSQL hogging resources?

From: "Jeremy Smith" <jer(at)highboard(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: PosgreSQL hogging resources?
Date: 2004-02-20 20:53:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin

One of the issues with my site is that many of the pages use iframes, so I
am actually loading up to 7 pages of varying database hungriness into the
browser at the same time.  I agree that pg with the triggers and procedures
should be able to adequately compete with mysql in terms of speed.  The
problem I am having is the complexity of the existing code combined with the
short amount of time that I have to get it to work.  Hopefully next
"offseason" I won't have as many new features do add and so will be able to
concentrate on optimization..

Anyway, I'm going to keep tinkering with pg offsite and I very much
appreciate all of the help and attention that I have been given from this


-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org]On Behalf Of Mitch Pirtle
Sent: Friday, February 20, 2004 3:24 PM
To: jer(at)highboard(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] PosgreSQL hogging resources?

Jeremy Smith wrote:

>I will look into some of the suggestions you have made, the problem is that
>I can't do large scale optimization at the moment because I am still adding
>features to the site.  I just wonder if the best mode of attack would be
>switching back to mysql until I have added all of the necessary features,
>optimizing the queries and code there, and then switching back to pg at a
>later date.
When you switch to pg, you will be able to move some/lots? of your code
into the database as views, stored procedures, triggers etc...  So keep
that in mind while working in MySQL, as you will definitely need a
different approach.

I inherited a site that had very database-hungry pages, and started
using stored procs and triggers to automate some of the jobs (like
updates and such) in the database, instead of making the webserver
manually send the instructions across the wire.  If you plan on taking
this approach then you should get your app into pg sooner than later...

-- Mitch, wondering about 12 packs?

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

pgsql-admin by date

Next:From: scott.marloweDate: 2004-02-20 20:56:39
Subject: Re: PosgreSQL hogging resources?
Previous:From: Joe MaldonadoDate: 2004-02-20 20:53:17
Subject: Re: database clustering

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