Search Postgresql Archives

Re: problem with a dropped database

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/14/06, Lee A Reum <areum.facu@xxxxxxxxx> 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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux