| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hubert Lubaczewski <depesz(at)depesz(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 14:22:51 |
| Message-ID: | CAMkU=1xLbimBPzP1xobkO-sUw2iELD3Emvn7zw0SwCYnkoSeSw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 13, 2016 at 6:36 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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
> discard prepared statements.
In the perl script he showed, the handle returned by $dbh->prepare is
not stored anywhere, so it should automatically get garbage collected
at the end of the Perl statement. The garbage collection should
trigger a destructor to send a "DEALLOCATE".
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-06-13 15:03:54 | Re: BUG #14184: Function is running correct but not showing output |
| Previous Message | torben | 2016-06-13 14:01:19 | BUG #14185: Indentation error in win32.mak let libpq compile fail on USE_OPENSSL=1 -- fix available |