| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] huge RAM use in multi-command ALTER of table heirarchy |
| Date: | 2017-07-20 12:39:11 |
| Message-ID: | CAM-w4HP9dtsM8GyoAgZhGLyXWAs30siUpoUg2n6+b6GcO4E0=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 19 July 2017 at 00:26, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's probably a bit late in the v10 cycle to be taking any risks in
> this area, but I'd vote for ripping out RememberToFreeTupleDescAtEOX
> as soon as the v11 cycle opens, unless someone can show an example
> of non-broken coding that requires it. (And if so, there ought to
> be a regression test incorporating that.)
Would it be useful to keep in one of the memory checking assertion builds?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-20 13:19:10 | Re: [GENERAL] huge RAM use in multi-command ALTER of table heirarchy |
| Previous Message | Thomas Kellerer | 2017-07-20 11:54:02 | _page_cost parameter with values < 1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2017-07-20 12:46:51 | Re: pg_upgrade failed if view contain natural left join condition |
| Previous Message | Fabrízio de Royes Mello | 2017-07-20 12:27:22 | Re: [PATCH] A hook for session start |