Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] [GENERAL] huge RAM use in multi-command ALTER of table heirarchy - Mailing list pgsql-hackers

From Greg Stark
Subject Re: [HACKERS] [GENERAL] huge RAM use in multi-command ALTER of table heirarchy
Date
Msg-id CAM-w4HP9dtsM8GyoAgZhGLyXWAs30siUpoUg2n6+b6GcO4E0=w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [GENERAL] huge RAM use in multi-command ALTER of table heirarchy  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] [GENERAL] huge RAM use in multi-command ALTER of table heirarchy
Re: [HACKERS] [GENERAL] huge RAM use in multi-command ALTER of table heirarchy
List pgsql-hackers
Tree view 
On 19 July 2017 at 00:26, Tom Lane <tgl@sss.pgh.pa.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

pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: [HACKERS] [PATCH] A hook for session start
Next
From: Thom Brown
Date:
Subject: Re: [HACKERS] pg_upgrade failed if view contain natural left join condition