| From: | G(dot)Bakalarski(at)icm(dot)edu(dot)pl |
|---|---|
| To: | "Kevin Grittner" <kgrittn(at)ymail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #8318: memory leak during CREATE TEMPORARY TABLE |
| Date: | 2013-07-31 08:24:40 |
| Message-ID: | 1e0b28053877c4a86f39784ed69d8514.squirrel@webmail.icm.edu.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> "g(dot)bakalarski(at)icm(dot)edu(dot)pl" <g(dot)bakalarski(at)icm(dot)edu(dot)pl> wrote:
>
>> When doing these kind of statements
>
>> execute <unnamed>: CREATE TEMPORARY TABLE [...]
>
>> After few days [...] my huge server (192GB of RAM), gets stucked
>> due to no memory available (usually %commit is around 103-105%),
>> linux OOM killer goes into action - it usually kills one of
>> postgres processes - postmaster restart all databases) and after
>> all linux has again some 100GB of not commited memory
>
> What do you have as settings for temp_buffers and max_connections?
>
temp_buffers = 16GB
max_connections = 250
(with real number of connections about 120 and not going above)
Grzegorz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Whiting | 2013-07-31 11:36:51 | Re: [BUGS] Incorrect response code after XA recovery |
| Previous Message | Albe Laurenz | 2013-07-31 07:37:35 | Re: Recovery_target_time misinterpreted? |