Alvaro Herrera writes:
> This text seems to work fine for released versions, but not very well
> for development, because it says this:
True.
> 3. add a separate paragraph that says to obtain the source from the
> other dir if it's the development one.
> I kinda prefer the last one, because then
On 2021-May-06, Jonathan S. Katz wrote:
> On 5/6/21 6:05 PM, Tom Lane wrote:
> > Alvaro Herrera writes:
> >> I agree -- if the user wanted packages, they would not be reading that
> >> page of the docs. I'd just have it point to the same page that the
> >> download page points to for source down
On 5/6/21 6:05 PM, Tom Lane wrote:
> Alvaro Herrera writes:
>> I agree -- if the user wanted packages, they would not be reading that
>> page of the docs. I'd just have it point to the same page that the
>> download page points to for source downloads, not a version-specific
>> one, as in the att
Alvaro Herrera writes:
> I agree -- if the user wanted packages, they would not be reading that
> page of the docs. I'd just have it point to the same page that the
> download page points to for source downloads, not a version-specific
> one, as in the attached patch.
+1. I think people reading
Hello
On 2021-May-04, Daniel Westermann (DWE) wrote:
> reading this: https://www.postgresql.org/docs/13/install-getsource.html
> ...
> I wonder if the link should not directly point to the relevant release, e.g.:
> https://www.postgresql.org/ftp/source/v13.2/
>
> To me that seems to be more conv
"David G. Johnston" writes:
> I did a read through of the patch and I like it; though I suggest changing
> "but non-NULL" to "while non-NULL".
Done that way, thanks.
regards, tom lane
Note that it is in general not necessary for the referencing column to
be NULLABLE. If you defer the constraint checking, you can insert a
cyclic structure. Of course, it's no longer a tree then.
The tutorial-ness of the documentation was already pointed out and I
don't think it needs to be said t
