Re: BUG #14234: PostgreSQL consuming large amount of memory for persistent connection

From: 德哥 <digoal(at)126(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14234: PostgreSQL consuming large amount of memory for persistent connection
Date: 2016-07-08 05:11:52
Message-ID: cb85153.681c.155c8eb4dde.Coremail.digoal@126.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

HI,
This is a reproduce method for why PostgreSQL session cann't release memory.
I have another case, has the same problem.
so i don't known why postgres cann't release memory? or can you explain these memory contain which objects? why use this design?
best regards,
digoal

--
公益是一辈子的事,I'm Digoal,Just Do It.

At 2016-07-08 10:01:18, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>digoal(at)126(dot)com writes:
>> why PostgreSQL session do not release these memory?
>> it will comsume these memory until disconnect.
>
>Your session has created and accessed 100000 tables plus 100000 views.
>I do not think you should complain if that takes a great deal of memory.
>Either rethink why you need so many tables, or buy hardware commensurate
>with the size of your problem.
>
> regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2016-07-08 06:08:16 Re: BUG #14234: PostgreSQL consuming large amount of memory for persistent connection
Previous Message nqtien310 2016-07-08 04:28:48 BUG #14236: pg_upgrade failed