| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL (9.3 and 9.6) eats all memory when using many tables |
| Date: | 2016-06-13 13:39:05 |
| Message-ID: | 20160613133905.GA16492@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 13, 2016 at 09:36:32AM -0400, Tom Lane wrote:
> Another problem, if the bloat is being driven by explicit PREPARE commands
> as you illustrate here, is that the backend doesn't get to silently
I did the same test with
$dbh->{pg_server_prepare} = 0;
(in pg logs, it changes logged lines from:
prepare <unnamed>:...
bind <unnamed>:...
execute <unnamed>:...
into:
statement:...
afterwards memory problems seemed to be the same.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | zzia88 | 2016-06-13 13:40:25 | BUG #14184: Function is running correct but not showing output |
| Previous Message | Tom Lane | 2016-06-13 13:36:32 | Re: PostgreSQL (9.3 and 9.6) eats all memory when using many tables |