On Tue, Mar 08, 2005 at 01:36:31PM +0200, Milen A. Radev wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> I have installed a script that executes vacuumdb for all DBs in my
> cluster (run by cron every night):
are you sure you're getting _every_ database? My bet is you're
missing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have installed a script that executes vacuumdb for all DBs in my
cluster (run by cron every night):
BEGIN
#!/bin/sh
# cron script to vacuum pgsql databases
#
PG_VACUUM_LOG=/var/log/pg_vacuum
echo St
Milen A. Radev wrote:
Of course you were both right - we found one small brain-dead perl
script that "executed an infinite loop in under 2 seconds" and in every
loop "pings" the DB using an empty query (well that's the implementation
in the perl pgsql driver). The responsible were punished.
So, whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Fuhr wrote:
> On Fri, Mar 11, 2005 at 12:06:16PM +0200, Milen A. Radev wrote:
>
>
>>Tom Lane wrote:
>>
>>
>>>So you managed to execute about 6000 transactions in those two seconds.
>>>Doing what?
>>
>>Well that could be the problem - I'm 99.9
On Fri, Mar 11, 2005 at 12:06:16PM +0200, Milen A. Radev wrote:
> Tom Lane wrote:
>
> > So you managed to execute about 6000 transactions in those two seconds.
> > Doing what?
>
> Well that could be the problem - I'm 99.99% positive we do not execute
> so many transactions - may be 30-40 thousand
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> So you managed to execute about 6000 transactions in those two seconds.
>> Doing what?
> Well that could be the problem - I'm 99.99% positive we do not execute
> so many transactions - may be 30-40 thousand per day and that's only f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
> "Milen A. Radev" <[EMAIL PROTECTED]> writes:
>
>>Two queries - 2 seconds apart:
>
>
>>template1=# SELECT datname, age(datfrozenxid) FROM pg_database;
>> datname | age
>>- ---+-
>> xxx1 | 1519763573
>
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
> Two queries - 2 seconds apart:
> template1=# SELECT datname, age(datfrozenxid) FROM pg_database;
> datname | age
> - ---+-
> xxx1 | 1519763573
> template1=# SELECT datname, age(datfrozenxid) FROM pg_database;
> dat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
> I wrote:
>
>>"Milen A. Radev" <[EMAIL PROTECTED]> writes:
>>
>>>I review the log every morning. In the beginning I got "wraparound
>>>failure" warnings every third day. But from a week I got those warnings
>>>every day. Well we have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Fuhr wrote:
> On Thu, Mar 10, 2005 at 11:19:03AM +0200, Milen A. Radev wrote:
>
>
>>exec /usr/local/pgsql/bin/vacuumdb -U postgres -h localhost \
>>- --all --analyze >>$PG_VACUUM_LOG 2>&1
>
>
> My first thought was that the lone hyphen at t
I wrote:
> "Milen A. Radev" <[EMAIL PROTECTED]> writes:
>> I review the log every morning. In the beginning I got "wraparound
>> failure" warnings every third day. But from a week I got those warnings
>> every day. Well we have one table in one database where there are a lot
>> of inserts, but not
On Thu, Mar 10, 2005 at 11:19:03AM +0200, Milen A. Radev wrote:
> exec /usr/local/pgsql/bin/vacuumdb -U postgres -h localhost \
> - --all --analyze >>$PG_VACUUM_LOG 2>&1
My first thought was that the lone hyphen at the beginning of the
script's last line might be causing an end of option processi
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
> I review the log every morning. In the beginning I got "wraparound
> failure" warnings every third day. But from a week I got those warnings
> every day. Well we have one table in one database where there are a lot
> of inserts, but not that many - aro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(This is a repost because the original was send when I was not
subscribed to the list and it is still not approved - sorry if you
received it already.)
I have installed a script that executes vacuumdb for all DBs in my
cluster (run by cron every nigh
14 matches
Mail list logo
