Thread

Commits

  1. doc: spell out full productname

  1. The use "Postgres" in docs

    Daniel Gustafsson <daniel@yesql.se> — 2023-03-14T11:22:40Z

    The docs use PostgreSQL and not Postgres in all but two places, which I think
    we should change like in the attached to be consistent. Any objections to this?
    
    --
    Daniel Gustafsson
    
    
  2. Re: The use "Postgres" in docs

    Alvaro Herrera <alvherre@alvh.no-ip.org> — 2023-03-14T11:31:49Z

    On 2023-Mar-14, Daniel Gustafsson wrote:
    
    > The docs use PostgreSQL and not Postgres in all but two places, which I think
    > we should change like in the attached to be consistent. Any objections to this?
    
    Both are very new.  No objection to the change.
    
    -- 
    Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
    
    
    
    
  3. Re: The use "Postgres" in docs

    Jonathan S. Katz <jkatz@postgresql.org> — 2023-03-14T12:55:43Z

    On 3/14/23 7:31 AM, Alvaro Herrera wrote:
    > On 2023-Mar-14, Daniel Gustafsson wrote:
    > 
    >> The docs use PostgreSQL and not Postgres in all but two places, which I think
    >> we should change like in the attached to be consistent. Any objections to this?
    > 
    > Both are very new.  No objection to the change.
    
    +1 -- good catch.
    
    Jonathan
    
    
  4. Re: The use "Postgres" in docs

    Daniel Gustafsson <daniel@yesql.se> — 2023-03-14T13:44:19Z

    > On 14 Mar 2023, at 13:55, Jonathan S. Katz <jkatz@postgresql.org> wrote:
    > 
    > On 3/14/23 7:31 AM, Alvaro Herrera wrote:
    >> On 2023-Mar-14, Daniel Gustafsson wrote:
    >>> The docs use PostgreSQL and not Postgres in all but two places, which I think
    >>> we should change like in the attached to be consistent. Any objections to this?
    >> Both are very new.  No objection to the change.
    > 
    > +1 -- good catch.
    
    Applied, thanks!
    
    --
    Daniel Gustafsson
    
    
    
    
    
  5. Nulls Not Distinct in Unique Indexes secton

    Kirk Parker <khp@equatoria.us> — 2023-03-14T15:24:25Z

    The Unique Indexes section (
    https://www.postgresql.org/docs/15/indexes-unique.html) does not mention
    the new NULLS [ NOT ] DISTINCT capability of indexes (
    https://www.postgresql.org/docs/15/sql-createindex.html), and it probably
    should.
    
    Specifically, it has the exact wording from previous versions (emphasis
    added):
    
        When an index is declared unique, multiple table
        rows with equal indexed values are not allowed.
        *Null values are not considered equal*.
    
    We should consider adding "unless the NULLS NOT DISTINCT clause is used
    when creating the index", or something to that effect.
    
  6. Re: Nulls Not Distinct in Unique Indexes secton

    Laurenz Albe <laurenz.albe@cybertec.at> — 2023-03-16T19:48:58Z

    On Tue, 2023-03-14 at 08:24 -0700, Kirk Parker wrote:
    > The Unique Indexes section (https://www.postgresql.org/docs/15/indexes-unique.html)
    > does not mention the new NULLS [ NOT ] DISTINCT capability of indexes
    > (https://www.postgresql.org/docs/15/sql-createindex.html), and it probably should.
    > 
    > Specifically, it has the exact wording from previous versions (emphasis added):
    > 
    >     When an index is declared unique, multiple table
    >     rows with equal indexed values are not allowed.
    >     *Null values are not considered equal*. 
    > 
    > We should consider adding "unless the NULLS NOT DISTINCT clause is used when
    > creating the index", or something to that effect.
    
    +1
    
    Here is a patch for that.
    
    Yours,
    Laurenz Albe