The Vacuum's don't take too long, 10 minutes at most. I can tell from ps
-ef | grep and top that its the selects/inserts/updates from the postgres
related to our app that take all that time up. If we rerun initdb and
reload the data, it works great for about two days, then goes bad again.
We a
I'm sorry all, when you say regular user as opposed to superuser are you
talking about the user that postgres is installed and running as? Should
this be done as the os's root?
Fabio
On Mon, 29 Mar 2004, Tom Lane wrote:
> "Marcus Andree S. Magalhaes" <[EMAIL PROTECTED]> writes:
> >> Also do yo
On Fri, 26 Mar 2004, Josh Berkus wrote:
> Fabio,
>
> > Recently it started eating up the cpu, and cannot keepup with the system
> > like it used to. The interesting thing here is that it still runs great
> > on an older system with less ram, one slower cpu, and an older disk.
>
> This really p
Hello fellow PostgreSQL users.
We've been working on this interesting issue for some time now, and we're
hoping that someone can help.
We've recently integrated postgres into an existing mature app. Its a
time sensitive 24x7 system. It runs on HP9000, a K370 Dual Processor
system. Postgres is
