Joe Maldonado <jmaldonado(at)webehosting(dot)biz> writes:
> I have these messages on my 7.4.7 database log...
> TopMemoryContext: 87494704 total in 10676 blocks; 179400 free (61
> chunks); 87315304 used
> TopTransactionContext: 57344 total in 3 blocks; 648 free (5 chunks);
> 56696 used
> DeferredTriggerXact: 0 total in 0 blocks; 0 free (0 chunks); 0 used
What's at the top and bottom of that?
PG prints out a memory stats dump like this when it runs out of memory.
The dump itself isn't much use to anyone but a developer; what you want
to look into is what triggered it. The error message appearing just
after (or maybe just before, I forget) should be relevant.
> followed by about 16GB of the following type of entries...
> pg_temp_1486707494: 2048 total in 1 blocks; 768 free (0 chunks); 1280 used
Could you have been trying to vacuum a ridiculously large number of
tables, or some such?
regards, tom lane
In response to
pgsql-general by date
|Next:||From: Tony Caduto||Date: 2005-04-28 22:43:42|
|Subject: Re: Postgresql and VBA vs Python|
|Previous:||From: Shelby Cain||Date: 2005-04-28 21:58:17|
|Subject: Increasing statistics results in worse estimates|