Re: Use <unnamed> for name of unnamed portal's memory context

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use <unnamed> for name of unnamed portal's memory context
Date: 2020-09-05 06:55:06
Message-ID: CAOBaU_ZqvUJXLQg6k_YrJDKHT1fHHMTfWcFB5rTSaVqdNbwSAg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Sep 5, 2020 at 8:25 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
> so 5. 9. 2020 v 8:14 odesílatel Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> napsal:
>>
>> I propose the attached little patch to set the name of the memory
>> context of an unnamed portal to "<unnamed>" instead of just an empty
>> string. Otherwise the debug memory context dump looks a little
>> confusing. We use this convention elsewhere for making unnamed
>> statements etc. more clearly visible.
>
>
> +1

+1 too, and obviously patch looks good.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2020-09-05 09:40:51 Re: New statistics for tuning WAL buffer size
Previous Message Pavel Stehule 2020-09-05 06:24:13 Re: Use <unnamed> for name of unnamed portal's memory context