Hello !
I used to run vacuum verbose analyze (vacuumdb -v -a -z) every days.
Everything was ok for months until yesterday !
Usually, this command takes about 1 mn.
Now, vacuum "blocks" on one table (apparently "comptes" table) , without HD
activity, no error message
avr 15 10:31:27 uranus
I have seen several postings in the list archives regarding this exact
issue but have never seen any response or resolution. We are running
pgsql 7.1.3 installed from the RedHat RPM on RedHat Linux 7.2. We are
running a fairly large accounting application written in PERl using the
PERL DBI and D
I would like to create multiple databases, each with its own disk location.
I have followed the instructions in the Administrator's Guide and have a
couple of questions.
1. Since the pg_ctl -D option only appears to take a single location, should
this be set to the location of the template1 da
Dear friends,
I seeking for benchmarks comparing PostgreSQL and other
databases of market, in special Oracle, to sugest PostgreSQL as server in a internal
project to my
University.
Does anyone knows where i find them?
Thanks for all.
[]'s
Edipo Elde
Running Postgres 7.1.4 from RedHad RPM on RedHat 7.2. When ever we run
a query where we are joining more than 3 tables the query never returns.
Any ideas?
Jeff
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgr
Jeff Madison wrote:
> Running Postgres 7.1.4 from RedHad RPM on RedHat 7.2. When ever we run
> a query where we are joining more than 3 tables the query never returns.
> Any ideas?
>
> Jeff
Jeff,
It would help to know things like:
* What the exact query is (and an EXPLAIN of the query)
*
"Jeff Madison" <[EMAIL PROTECTED]> writes:
> ... What we are seeing is when
> people terminate the application in the middle of a query many times
> postmaster does not see the connection terminate or at least ignores it
> and then proceeds to take a large amount of system resources and never
> d
Charlie Toohey <[EMAIL PROTECTED]> writes:
> 1. Since the pg_ctl -D option only appears to take a single location, should
> this be set to the location of the template1 database created as part of the
> Postgres installation, or, do I have to somehow specify the location of each
> of my databas