From: Wei Weng <wweng@kencast.com>
To: pgsql-sql@postgresql.org
Subject: Re: Seeking advice regarding a design problem
Date: 02 Aug 2002 12:21:12 -0400
Message-ID: <1028305273.9762.33.camel@Monet> (raw)
In-Reply-To: <1028305002.9763.31.camel@Monet>
References: <1028305002.9763.31.camel@Monet>
Forgot to mention, the version of postgresql I am running is 7.1.3.
On Fri, 2002-08-02 at 12:16, Wei Weng wrote:
> I am running postgresql as database backend, and I have some scripts
> dealing with constant incoming data and then insert these data into the
> database, in a quite complex way, involving a couple of procedures.
>
> But the performance of the database is worse than I had thought. After
> about 100 times of the script being run, the speed of the insertion
> slowed down dramatically. But it went back to the regular fast speed
> after I did a vacuum analyze.
>
> how can I redesign the system to avoid the bottleneck? And why is it
> that postgresql can slow down so much after doing some complex
> operations?
>
>
> Thanks
>
>
> --
> Wei Weng
> Network Software Engineer
> KenCast Inc.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Wei Weng
Network Software Engineer
KenCast Inc.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: wweng@kencast.com
Subject: Re: Seeking advice regarding a design problem
In-Reply-To: <1028305273.9762.33.camel@Monet>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox