Look at the documentation here:
http://www.postgresql.org/docs/7.4/interactive/maintenance.html
The upshot is that you should vacuum every table in the database at
least once every billion transaction. It doesn't have to be a VACUUM
FULL, just run VACUUM without specifying a table.
There's some
Martijn van Oosterhout wrote:
Let's start with the version of postgresql you're using.
Next, were you running VACUUM FULL regularly?
It sounds like XID wraparound to me, no idea how to solve that. Got
backups?
On Wed, Nov 10, 2004 at 12:56:33PM +0200, Liviu BURCUSEL wrote:
Hi !
I'm in the ultimate
On Wed, 10 Nov 2004 08:11:01 -0800 (PST)
Jeff Eckermann <[EMAIL PROTECTED]> wrote:
> --- Liviu BURCUSEL <[EMAIL PROTECTED]> wrote:
>
> > Hi !
> >
> > I'm in the ultimate state of dispair. Over the night
> > some of my
> > databases just disapeared. But they did not dissaper
> > totally. I can
>
--- Liviu BURCUSEL <[EMAIL PROTECTED]> wrote:
> Hi !
>
> I'm in the ultimate state of dispair. Over the night
> some of my
> databases just disapeared. But they did not dissaper
> totally. I can
> still connect to them but I cannot dump them. When
> doing a "select *
> from pg_database" I see onl
Let's start with the version of postgresql you're using.
Next, were you running VACUUM FULL regularly?
It sounds like XID wraparound to me, no idea how to solve that. Got
backups?
On Wed, Nov 10, 2004 at 12:56:33PM +0200, Liviu BURCUSEL wrote:
> Hi !
>
> I'm in the ultimate state of dispair. Ove
Hi !
I'm in the ultimate state of dispair. Over the night some of my
databases just disapeared. But they did not dissaper totally. I can
still connect to them but I cannot dump them. When doing a "select *
from pg_database" I see only 2 databases I hardly ever use (they are
used once in a couple o
