On Sat, 06 Oct 2007 23:05:23 -0700, "Joshua D. Drake"
> Darren Reed wrote:
> > I'm starting to wonder if my database has finally grown too big for my
> > computer.
> > But, rather than peform badly, I see a number of "bad things" happen:
> > * pg_dump fails to run, causing an "out of memory" error (I don't
> > understand
> > why this happens, but it does);
> > * restarting postgres across a reboot results in tables disappearing
> > without any error messages being given out (this is *really
> > disturbing*.)
> Are you vacuuming?
No. I'm just using the standard config
If you're implying I should?
The problems I've come across have become evident with as little work as
- run "initdb"
- start postgres
- run "psql" to import the dumped data
- run for a short period of time (less than an hour)
- shutdown postgres
- postgres starts
- the large tables are now missing
With the above, I wouldn't have thought there is enough time to do
which seem to take quite a while on large tables. The activity is a
of inserts and updates (from triggers and plsql functions.)
In response to
pgsql-admin by date
|Next:||From: Scott Marlowe||Date: 2007-10-07 08:14:10|
|Subject: Re: Is my database now too big?|
|Previous:||From: Suresh Gupta VG||Date: 2007-10-07 07:10:26|
|Subject: Re: Postgresql takes more time to update|