pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Matthias Otterbach <mo@otterbach.eu>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage when selecting BYTEA data (maybe memory leak)
Date: Mon, 18 Mar 2019 16:16:47 -0400
Message-ID: <12020.1552940207@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMkU=1wW32K8n4ut_7zz+6HH1J068tFtpv5os=eeAgvjiQH8ZQ@mail.gmail.com>
References: <15700-8c408321a87d56bb@postgresql.org>
	<16717.1552926811@sss.pgh.pa.us>
	<4ef5f38d5710c4d5c289537c588c7335@otterbach.eu>
	<CAMkU=1wW32K8n4ut_7zz+6HH1J068tFtpv5os=eeAgvjiQH8ZQ@mail.gmail.com>

Jeff Janes <jeff.janes@gmail.com> writes:
> Doing that, I can reproduce the problem, and it seems to be using an
> implicitly declared cursor (which I have not run into before).

Hm, I'd tried a manually declared cursor w/ FETCH commands, but apparently
this way is different.  Thanks for the confirmation.

			regards, tom lane




view thread (16+ messages)  latest in thread

Message-ID: <12020.1552940207@sss.pgh.pa.us>
Permalink:  ../12020.1552940207@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12020.1552940207@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jeff.janes@gmail.com, mo@otterbach.eu, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage when selecting BYTEA data (maybe memory leak)
  In-Reply-To: <12020.1552940207@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox