pg_prewarm
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/pgprewarm.html Description: To be added to the documentation: - Default location of autoprewarm.blocks - Configure the location of autoprewarm.blocks - How often does it dump the block id's of the buffer cache? - Can this interval be adapted? Use case: how to easily set it up to load the buffer cache with the blocks just before shutdown of the DB.
Re: Simplify COMMENT and SECURITY LABEL documentation
Peter Eisentraut writes: > ... I wonder if it would be more practical to just write: > The name of the object to be commented. Names of objects that live > in schemas (tables, functions, etc.) can be schema-qualified. +1 for the concept, but I feel that "live in" is a bit too informal for this context. I'm too caffeine-deprived to instantly come up with le mot juste; but perhaps "exist within" would be an improvement? regards, tom lane
Re: Simplify COMMENT and SECURITY LABEL documentation
On 2021-Jun-01, Tom Lane wrote: > Peter Eisentraut writes: > > ... I wonder if it would be more practical to just write: > > > The name of the object to be commented. Names of objects that live > > in schemas (tables, functions, etc.) can be schema-qualified. > > +1 for the concept, but I feel that "live in" is a bit too informal > for this context. I'm too caffeine-deprived to instantly come up > with le mot juste; but perhaps "exist within" would be an improvement? The glossary uses "reside in". Schema A schema is a namespace for SQL objects, which all reside in the same database. Each SQL object must reside in exactly one schema. I suppose that we should either use the same term that the glossary uses, or alternatively fix the glossary to use whatever term we decide to use here. I do notice now that I used the term "belong to" elsewhere in the glossary. That could use some cleanup. SQL object Any object that can be created with a CREATE command. Most objects are specific to one database, and are commonly known as local objects. Most local objects belong to a specific schema in their containing database, such as relations (all types), routines (all types), data types, etc. The names of such objects of the same type in the same schema are enforced to be unique. There also exist local objects that do not belong to schemas; some examples are extensions, data type casts, and foreign data wrappers. The names of such objects of the same type are enforced to be unique within the database. -- Álvaro Herrera39°49'30"S 73°17'W "No renuncies a nada. No te aferres a nada."
Re: Simplify COMMENT and SECURITY LABEL documentation
Alvaro Herrera writes: > On 2021-Jun-01, Tom Lane wrote: >> +1 for the concept, but I feel that "live in" is a bit too informal >> for this context. I'm too caffeine-deprived to instantly come up >> with le mot juste; but perhaps "exist within" would be an improvement? > The glossary uses "reside in". > ... > I suppose that we should either use the same term that the glossary > uses, or alternatively fix the glossary to use whatever term we decide > to use here. Yeah, having a standard phrasing would be good. > I do notice now that I used the term "belong to" elsewhere in the > glossary. That could use some cleanup. Hmm, I like "belong to" better than these others. Maybe we should standardize on that? regards, tom lane
