Greg Stark writes:
> Were the latest round of infinite recursion in
> the character conversion routines in 8.3.7?
Yes, and in any case the typical symptom of that problem was a SIGSEGV
(due to stack overrun) not an out-of-memory complaint.
regards, tom lane
--
Sent vi
The link was to the memory context dump. The only suspicious context I
spotted was 300mb in MessageContext. What is lc_messages and lc_ctype
set to on this machine? Were the latest round of infinite recursion in
the character conversion routines in 8.3.7?
--
Greg
On 26 May 2009, at 17:00,
Pavel Stehule writes:
> one czech PostgreSQL user reports problem with memory - probable memleak?
> Is possible to diagnose some from log?
If he's getting an actual "out of memory" error, let's see the memory
context map that gets dumped to the server log (or more specifically,
to stderr).
> Ser
Hello
one czech PostgreSQL user reports problem with memory - probable memleak?
Is possible to diagnose some from log?
Postgres ver. 8.3.7 .
Server 8G RAM, 32b Debian Etch.
Configuration:
shared_buffers = 324000# min 16 or max_connections*2, 8KB each
temp_buffers = 16000#
