| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Kohei KaiGai <kaigai(at)heterodb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is custom MemoryContext prohibited? |
| Date: | 2020-01-29 02:53:58 |
| Message-ID: | 10182.1580266438@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Tue, Jan 28, 2020 at 10:09 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> No. No. Just NO. (A) that's overly complex for developers to use,
>> and (B) you have far too much faith in the debugger producing something
>> useful. (My experience is that it'll fail to render function pointers
>> legibly on an awful lot of platforms.) Plus, you won't actually save
>> any space by removing both of those fields.
> FWIW, I noticed that GDB becomes much better at this when you add "set
> print symbol on" to your .gdbinit dot file about a year ago.
Interesting. But I bet there are platform and version dependencies
in the mix, too. I'd still not wish to rely on this for debugging.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-01-29 03:02:22 | Don't try fetching future segment of a TLI. |
| Previous Message | Tom Lane | 2020-01-29 02:46:08 | Re: Hash join not finding which collation to use for string hashing |