Hello, On 2024-Dec-13, Yuya Watari wrote:
> Thank you for your reply, and I'm sorry if my previous emails caused > confusion or made it seem like I was ignoring more important issues. Not to worry! > > Memory usage and planning time in production builds [are] important. > > You can better spend your energy there. > > As you said, we have another big problem, which is memory usage. I > will focus on the memory usage problem first, as you suggested. That's great, thanks. BTW I forgot to mention it yesterday, but I was surprised that you attached Ashutosh's old patch for planner memory usage reporting. This feature is already in EXPLAIN (MEMORY), so you don't need any patch to measure memory consumption ... or does your patch add some detail that isn't already in the code? > After fixing those problems, we can revisit the assert-enabled build > regressions as a final step if necessary. What do you think about this > approach? Sounds good. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "I can't go to a restaurant and order food because I keep looking at the fonts on the menu. Five minutes later I realize that it's also talking about food" (Donald Knuth)
