| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Guangzhou Zhang <35514815(at)qq(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: Unexpected memory usage for repeated inserts within plpgsql function |
| Date: | 2016-07-23 01:14:25 |
| Message-ID: | CAFiTN-tHgvf-2XFyA+DKpMLyWy-KTTSMKoJ9rnPq7LzWfE3ZPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 22, 2016 at 4:06 PM, Guangzhou Zhang <35514815(at)qq(dot)com> wrote:
> Thank you. Yes when I correctly created the table (so avoiding insertion
> statement error), the memory usage went no higher than ~ 60MB.
>
> Is this a bug from your point of view?
>
On other thread there are discussion going on about how to fix this issue.
You can refer this thread.
/message-id/17863.1469142152%40sss.pgh.pa.us
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-07-23 01:31:04 | Re: Design for In-Core Logical Replication |
| Previous Message | David G. Johnston | 2016-07-23 01:05:49 | Re: Proposal: revert behavior of IS NULL on row types |