Re: Tips about using mount point directly as the data_directory.

Sorry, this information hides a little bit deep inside the document, I tried my best to find this but missed. David G. Johnston 于2020年11月10日周二 下午10:23写道： > On Tuesday, November 10, 2020, PG Doc comments form < > nore...@postgresql.org> wrote: > >> The following documentation comment has been

Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html

On Tue, Nov 10, 2020 at 06:15:29PM -0500, Tom Lane wrote: > Bruce Momjian 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

Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html

Bruce Momjian writes: > On Tue, Nov 10, 2020 at 06:15:29PM -0500, Tom Lane wrote: >> That is the path underneath the installation "include" directory >> at which that file will be found. > Uh, I don't see it: > $ ls -w 80 /usr/local/pgsql/include/ > ecpg_config.hlibpq

Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html

On Tue, Nov 10, 2020 at 06:15:29PM -0500, Tom Lane wrote: > Bruce Momjian 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

Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html

Bruce Momjian 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

Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html

On Fri, Oct 30, 2020 at 11:09:58AM -0400, Tom Lane wrote: > Euler Taveira writes: > > On Tue, 27 Oct 2020 at 13:54, Bruce Momjian wrote: > >> Uh, in my source tree that is a symlink to > >> src/backend/catalog/pg_type_d.h, but that file is generated by > >> src/backend/catalog/genbki.pl. Does

Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?

On Mon, Nov 9, 2020 at 08:36:32PM -0500, Bruce Momjian wrote: > On Tue, Nov 3, 2020 at 06:11:21PM +, Chris Wilson wrote: > > Hi all, > > > > I did some more research and found this explanation in a presentation by > > 2ndQuadrant: > > > > > > When a process wants a buffer, it asks

Re: Tips about using mount point directly as the data_directory.

On Tuesday, November 10, 2020, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/bug-reporting.html > Description: > > Using a mount point directly as the data_directory is not recommended, but > this

'pg_global' cannot be used as default_tablespace.

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/bug-reporting.html Description: Tablespace 'pg_global' is one of the two auto-generated tablespace by initdb, and 'pg_global' should not be used as the default_tablespace, since it is

Tips about using mount point directly as the data_directory.

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/bug-reporting.html Description: Using a mount point directly as the data_directory is not recommended, but this tip is not recorded in the doc

The relationship between 'min_wal_size', 'max_wal_size' and 'wal_segment_size' is not record.

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/bug-reporting.html Description: configuration option 'min_wal_size' and 'max_wal_size' must be at least twice 'wal_segment_size', but none of these information was mentioned in the