Re: Trying to Tunning DB

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: "Cristina Surroca" <cris(at)dmcid(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Trying to Tunning DB
Date: 2003-04-05 17:08:42
Message-ID: r92u8vottk6suhdp6ti980su9el6e12bph@4ax.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 5 Apr 2003 16:15:37 +0200, "Cristina Surroca" <cris(at)dmcid(dot)net>
wrote:
> It hasn't any delete, only inserts (more than 10^7) and many updates.

10^7 inserts per day? If it has updates, it implicitly has deletes.
How *many* updates?

> The thing is that it takes too much time in execute.

We can help you better, if you show us some actual SQL.

> b.. setAutocommit(false), ( in my case I don't need transactions).

There is no I_dont_need_transactions mode in Postgres. You always
have transactions. Either you control them or Postgres performs each
statement in its own transaction. As far as I understand, autocommit
off means that you don't have to say BEGIN to start a transaction and
the transaction stays active until you COMMIT. Your application or
JDBC might do this automatically.

> But in my case, would you think vacuum and analyze are good options?

Definitely!

> Can I also disable the catalog?

I don't know what you mean, but I am pretty sure, you can't.

Servus
Manfred

In response to

Browse pgsql-general by date

  From Date Subject
Next Message nolan 2003-04-05 17:38:20 Re: dbmirror revisions
Previous Message Cristina Surroca 2003-04-05 14:15:37 Trying to Tunning DB