Re: Obsolete comment in pg_stat_statements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Obsolete comment in pg_stat_statements
Date: 2024-09-14 15:44:23
Message-ID: 276845.1726328663@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Sat, 14 Sept 2024, 12:39 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hmm ... I agree that para is out of date, but is there anything to
>> salvage rather than just delete it?

> I thought about it but I think that now that knowledge is in the else
> branch, with the mention that we still have to bump the nesting level even
> if it's not locally handled.

After sleeping on it I looked again, and I think you're right,
there's no useful knowledge remaining in this para. Pushed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2024-09-14 17:37:11 Re: Psql meta-command conninfo+
Previous Message Alexander Lakhin 2024-09-14 15:00:00 Re: Robocopy might be not robust enough for never-ending testing on Windows