Re: Is custom MemoryContext prohibited?
От | Tom Lane |
---|---|
Тема | Re: Is custom MemoryContext prohibited? |
Дата | |
Msg-id | 10182.1580266438@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Is custom MemoryContext prohibited? (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: Is custom MemoryContext prohibited?
Re: Is custom MemoryContext prohibited? |
Список | pgsql-hackers |
Peter Geoghegan <pg@bowt.ie> writes: > On Tue, Jan 28, 2020 at 10:09 AM Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-hackers по дате отправления: