Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Tony Caduto wrote:
I did not have autovacuum turned on and I usually do a vacuumdb -z -a -f
-q each night but this one slipped through the cracks :-(
Strange -- autovacuum should have started an automatic database-
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tony Caduto wrote:
>> I did not have autovacuum turned on and I usually do a vacuumdb -z -a -f
>> -q each night but this one slipped through the cracks :-(
> Strange -- autovacuum should have started an automatic database-wide
> vacuum on that databas
Tony Caduto wrote:
> Martijn van Oosterhout wrote:
> >On Mon, Nov 27, 2006 at 02:22:19PM -0600, Tony Caduto wrote:
> >
> >>Just in case anyone is interested I did get it up and running with no
> >>damage to the system.
> >>It took well over a year for it to reach the 1 million threshold mark.
Martijn van Oosterhout wrote:
On Mon, Nov 27, 2006 at 02:22:19PM -0600, Tony Caduto wrote:
Just in case anyone is interested I did get it up and running with no
damage to the system.
It took well over a year for it to reach the 1 million threshold mark.
You mean one *billion*, right?
On Mon, Nov 27, 2006 at 02:22:19PM -0600, Tony Caduto wrote:
> Just in case anyone is interested I did get it up and running with no
> damage to the system.
> It took well over a year for it to reach the 1 million threshold mark.
You mean one *billion*, right?
That's one busy server!
Hopeeful
Alvaro Herrera wrote:
Stop the postmaster, start a standalone backend, and issue a
database-wide VACUUM on database postgres.
Just in case anyone is interested I did get it up and running with no
damage to the system.
It took well over a year for it to reach the 1 million threshold mark.
T
On Mon, 2006-11-27 at 13:36 -0600, Tony Caduto wrote:
> Alvaro Herrera wrote:
> > Tony Caduto wrote:
> >
> >> I don't know what the exact version is but I am getting this:
> >>
> >> FATAL: database is not accepting commands to avoid wraparound data loss
> >> in database "postgres"
> >>
> >> Ho
Alvaro Herrera wrote:
Tony Caduto wrote:
I don't know what the exact version is but I am getting this:
FATAL: database is not accepting commands to avoid wraparound data loss
in database "postgres"
How can I recover from this and why woud this happen to the postgres
database? Has my se
Tony Caduto wrote:
> I don't know what the exact version is but I am getting this:
>
> FATAL: database is not accepting commands to avoid wraparound data loss
> in database "postgres"
>
> How can I recover from this and why woud this happen to the postgres
> database? Has my server been hacke
I don't know what the exact version is but I am getting this:
FATAL: database is not accepting commands to avoid wraparound data loss
in database "postgres"
How can I recover from this and why woud this happen to the postgres
database? Has my server been hacked? there should be no inserts
10 matches
Mail list logo
