| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | alex <alex(dot)pgsql(at)kerkhove(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: postgres 'forgets' table definitions |
| Date: | 2008-06-10 15:52:29 |
| Message-ID: | dcc563d10806100852r71e6d58fl6da36fe856826cbb@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Jun 10, 2008 at 7:59 AM, alex <alex(dot)pgsql(at)kerkhove(dot)net> 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 to this pg_* tables/vacuum issue)
As Jaime mentioned already, vacuuming is required. However, in
addition to his point about various improvements, newer version will
begin throwing errors as they get closer to txid wraparound, and will
eventually shut down and refuse to run in multi-user mode once it
reaches a certain point.
So, yes, things have improved.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dinesh | 2008-06-10 16:52:27 | error handling unique key constraint in pgsql |
| Previous Message | Jaime Casanova | 2008-06-10 15:19:32 | Re: postgres 'forgets' table definitions |