From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | jadel(at)mercury(dot)com |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [PATCH] docs: Document the automatically generated names for indices |
Date: | 2022-09-02 15:46:32 |
Message-ID: | YxIlWKpqcF6cLYHX@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 1, 2022 at 05:47:11PM -0700, jadel(at)mercury(dot)com wrote:
> From: Jade Lovelace <jadel(at)mercury(dot)com>
>
> I have intentionally been careful to not guarantee that the
> automatically generated name *is* what's documented, but instead give
> the general idea.
>
> Knowing the format is useful for people writing migrations/ORM tools
> which need to name their unique indices and may wish to use the
> automatic naming system.
Uh, I always that if people didn't want to specify an index name, that
they didn't care. I think there are enough concurrency issues listed
below that I don't see the value of documenting this. If they really
care, they can look at the source code.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-09-02 15:52:38 | walmethods.c/h are doing some strange things |
Previous Message | Daniel Gustafsson | 2022-09-02 15:36:55 | Re: On login trigger: take three |