From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Primary Key index |
Date: | 2010-08-18 16:23:00 |
Message-ID: | AANLkTikPUSN0C_kgu1J42AKNXRhArpKp6uPttDXjwYsf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 18 August 2010 17:09, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Thom Brown <thom(at)linux(dot)com> wrote:
>
>> In response to a user asking a question about indexes on primary
>> keys
>>
> (http://archives.postgresql.org/pgsql-performance/2010-08/msg00194.php)
>> I attach a patch to add information to the Primary Keys section of
>> the Constraints page. While the information already exists on the
>> CREATE TABLE, I don't think a brief mention on the page specifically
>> concerning primary keys could hurt.
>>
>> So here's a patch to add it. Worth adding?
>
> I think so, but I think we should cover UNIQUE constraints, too. I
> was also thinking about possibly mentioning it in the index overview
> page, and adding an entry or two to the documentation index, but
> maybe that's overkill.
>
Well I guess the question is: "where will most people first look to
find that piece of information out?"
As long as the information isn't digressing from the topic it's
mentioned in, I don't see the problem. :)
--
Thom Brown
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-08-18 16:24:12 | Re: PDF docs text overflowing |
Previous Message | Kevin Grittner | 2010-08-18 16:09:25 | Re: Primary Key index |