Re: Patch a potential memory leak in describeOneTableDetails()

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: daniel(at)yesql(dot)se
Cc: wliang(at)stu(dot)xidian(dot)edu(dot)cn, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Patch a potential memory leak in describeOneTableDetails()
Date: 2022-02-24 06:32:01
Message-ID: 20220224.153201.718114260358756931.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 24 Feb 2022 14:44:56 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> At Tue, 22 Feb 2022 09:59:09 +0100, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote in
> > The section in question was added to our docs 22 years ago, to make it reflect
> > the current operating systems in use maybe just not mentioning more(1) is the
> > easiest?:
> >
> > "The text browsing tool less can be invoked as less -x4 to make it show
> > tabs appropriately."
> >
> > Or perhaps remove that section altogether?
>
> I think the former is better.

So the attached does that.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-02-24 06:32:55 Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset
Previous Message Etsuro Fujita 2022-02-24 05:49:12 Re: postgres_fdw: commit remote (sub)transactions in parallel during pre-commit