From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com>, e(dot)indrupskaya(at)postgrespro(dot)ru, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html |
Date: | 2020-11-12 20:13:26 |
Message-ID: | 20201112201326.GD4506@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Nov 10, 2020 at 07:23:12PM -0500, Bruce Momjian wrote:
> On Tue, Nov 10, 2020 at 06:15:29PM -0500, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > On Fri, Oct 30, 2020 at 11:09:58AM -0400, Tom Lane wrote:
> > >> Thinking about it from the perspective of someone dealing with an
> > >> installation tree not a source tree, maybe the reference should
> > >> be to "server/catalog/pg_type_d.h". That might help disabuse
> > >> anyone who's expecting to find it at that path in the git tree.
> >
> > > I am confused what the "server/" prefix means in a path name.
> >
> > That is the path underneath the installation "include" directory
> > at which that file will be found.
>
> Yep, it's there. I thought I checked for an include/catalog install
> directory, but obviously not well enough.
>
> > > We currently say:
> >
> > > The <acronym>OID</acronym>s of the built-in data types are defined in
> > > the file <filename>src/include/catalog/pg_type_d.h</filename> in the
> > > source tree.
> >
> > Yeah, so also s/source tree/install tree/.
>
> OK, here is a patch that mentions both.
Adjusted patch applied to all branches.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2020-11-13 13:16:55 | tables have merged columns |
Previous Message | Bruce Momjian | 2020-11-12 17:37:30 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |