The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/catalogs-overview.html
Description:
The documentation for chapter 52 does not clearly identify the schema
associated with the system catalogs in either the chapter header or overview
secti
I see how that can be pretty useful for something that's as simple as
asciidoc. But I wonder how useful it would be for our docbook documentation.
There'd be no preview (which there i sin the elastic), and we know how
difficult it can be to get the tags right without running test builds even
for t
> On 4 May 2020, at 19:06, Magnus Hagander wrote:
> Question is if the benefit would outweigh the cost, compared to just receiving
> comments and "manually patching them in".
Another question is the cost of managing access to such a system, we haven't
exactly had the best of luck with input from
(accidentally sent my last post without the links at the bottom, fixed)
Daniel and Magnus, thanks for your replies. Here's my personal 2-click
submission "ideal scenario", that may differ from other contributors, but
seems to be very common now for many FOSS projects. I think this will work
for
Daniel and Magnus, thanks for your replies. Here's my personal 2-click
submission "ideal scenario", that may differ from other contributors, but
seems to be very common now for many FOSS projects. I think this will work
for the vast majority of the documentation pages. Note that this is not a
wi
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/functions-math.html
Description:
Proposed rewording for ceil() and ceiling(): "smallest integer..."
Proposed rewording for floor(): "greatest integer..."
Rationale: the proposed rewording
As of HEAD, building the PDF docs for A4 paper draws 538 "contents
... exceed the available area" warnings. While this is a nice step
forward from where we were (v12 has more than 1500 such warnings),
we're far from done fixing that issue.
A large chunk of the remaining warnings are about tables
On 5/4/20 9:52 PM, Tom Lane wrote:
> As of HEAD, building the PDF docs for A4 paper draws 538 "contents
> ... exceed the available area" warnings. While this is a nice step
> forward from where we were (v12 has more than 1500 such warnings),
> we're far from done fixing that issue.
>
> A large ch
PG Doc comments form writes:
> Proposed rewording for ceil() and ceiling(): "smallest integer..."
> Proposed rewording for floor(): "greatest integer..."
> Rationale: the proposed rewording is more aligned to their respective
> mathematical definitions
Actually, that's very nearly the wording we
On Sun, May 03, 2020 at 03:53:31PM +0900, Michael Paquier wrote:
> Fine for me as well as far as it goes. I'll go apply it if there are
> no objections.
And done.
--
Michael
signature.asc
Description: PGP signature
Hello Tom,
oid oid
Row identifier
adrelid oid (references pg_class.oid)
The table this column belongs to
adnum int2 (references pg_attribute.attnum)
The number of the column
adbin pg_node_tree
The column default value, in nodeToString() representation. Use
11 matches
Mail list logo
