Re: problem with a dropped database

From: "Jaime Casanova" <systemguards(at)gmail(dot)com>
To: "Lee A Reum" <areum(dot)facu(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: problem with a dropped database
Date: 2006-08-14 17:07:20
Message-ID: c2d9e70e0608141007o450ea333rac98fc77d1cf9906@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/14/06, Lee A Reum <areum(dot)facu(at)gmail(dot)com> wrote:
>
> Hi,
> I need your help!
>
> I vacuumed an entire database because it was having a transaction wraparound
> problem.
> Then I dropped the database.
>
> After running ANALYZE, the entry of the database is gone as I expected.
> But when I try to connect to other databases I get the same transaction
> wraparound error message for the database that doesn´t exsit anymore.
>
> Can anybodoy help me with finding out what´s wrong?
>

from docs:
"When any database approaches the billion-transaction danger level,
the system begins to emit warning messages."

so, maybe the database you vacuum wasn't the culprit... vacuum the
other databases may help (template1 included, i'm not sure if is
really necessary but...)

--
regards,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Reece Hart 2006-08-14 18:04:30 text datum VARDATA and strings
Previous Message Jorge Godoy 2006-08-14 16:37:28 Re: Best approach for a "gap-less" sequence