| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15321: XMLTABLE leaks memory like crazy |
| Date: | 2018-08-13 13:38:46 |
| Message-ID: | 20180813133846.eahlw6z6zxif3eiv@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2018-Aug-13, Andrew Gierth wrote:
> >>>>> "Andrew" == Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
>
> Tom> But maybe fetchRowsCxt or tableBuildCxt or something along that
> Tom> line? It's not very clear what "perCall" is per call of, so I'm
> Tom> not in love with that idea.
>
> Andrew> Meh. perTableCxt?
>
> Pushed it with perTableCxt as the name.
Thanks for taking care of this! Much appreciated.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-08-13 14:37:00 | BUG #15323: wal_keep_segments must be >= 1 for WAL archiving + streaming to work |
| Previous Message | Andrew Gierth | 2018-08-13 01:22:46 | Re: BUG #15321: XMLTABLE leaks memory like crazy |