On Tue, Jun 10, 2008 at 7:59 AM, alex <[EMAIL PROTECTED]> wrote:
> Problem solved!
>
> Even without vacuuming, I don't think postgres should ever behave like this,
> but I'm glad my problem is solved now.
>
> (perhaps this issue is fixed in newer releases, if not someone might want to
> look in t
On Tue, Jun 10, 2008 at 8:59 AM, alex <[EMAIL PROTECTED]> wrote:
> Problem solved!
>
> After a vacuum full verbose analyze of all the pg_* tables everything is fine
> again.
>
> I switched to a scripted vacuum about 6 months ago because some
> (history)tables take way too long to vacuum and have
sue)
alex.
Original Message
Subject: [ADMIN] postgres 'forgets' table definitions
From: alex <[EMAIL PROTECTED]>
To: [email protected]
Date: Tue Jun 10 2008 13:12:32 GMT+0200
> Hi,
>
> We're running pgsql 7.3.14 (yes I know it's ol
Hi,
We're running pgsql 7.3.14 (yes I know it's old, an upgrade to 8.3 is planned).
Since a couple of weeks postgres loses the table definitions from apparently
random tables. A 'broken' table actually still works but a \d table gives
nothing. Currently The biggest problem is that these broken
Hi,
We're running pgsql 7.3.14 (yes I know it's old, an upgrade to 8.3 is planned).
Since a couple of weeks postgres loses the table definitions from apparently
random tables. A 'broken' table actually still works but a \d table gives
nothing. Currently The biggest problem is that these broken
