Message-ID: <8a47be1e-4d12-4eb8-b3d6-90371a715ebc@postgresfriends.org>
Date: Fri, 13 Oct 2023 02:48:28 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: SQL:2011 application time
Content-Language: en-US
To: Paul Jungwirth <pj@illuminatedcomputing.com>,
 Peter Eisentraut <peter@eisentraut.org>,
 jian he <jian.universality@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
 <7d44dade-ff31-5eef-80ac-78ed838066f6@postgresfriends.org>
 <88dadcc1-6652-ff7d-264d-73906a53dee9@illuminatedcomputing.com>
 <CACJufxHD2kv6hCy8yjVk486+d5rcuJS2XxkNH80g9Ui6Rz81Cg@mail.gmail.com>
 <CACJufxFTqiag-4fDPWJLxwwX+2gcZZWJPM9GyhPYD0tH=uM+jQ@mail.gmail.com>
 <CA+renyV4RxkWx57Vi5k_k0d7mkT7+F2kHYuKkwNPBaSOCaotFA@mail.gmail.com>
 <CACJufxG7DKLhyJgBaFttdXZe-4dOVu3NVED+4sdegdGs6R7JdQ@mail.gmail.com>
 <CACJufxFxQH5NxD9UDvbcRCPtaSga+y0+Wwt54PA4KahLwhahOA@mail.gmail.com>
 <5157e85a-6007-27a7-853a-5601d9c3722f@illuminatedcomputing.com>
 <CACJufxGCWDSK2pYMwNdsyDGk6skbP_L5yvSBK67L6pxbGUF8OQ@mail.gmail.com>
 <5a16a59a-d497-7d72-07aa-0afc09d5193a@illuminatedcomputing.com>
 <CACJufxG_iZc8hbdcfjkU6q81kLf4R2Fp=VyDZbyhocuTbMNVEw@mail.gmail.com>
 <b8ef855d-216b-5499-6a6e-ec883a32bd96@illuminatedcomputing.com>
 <1106ff18-b607-7ff3-e4ab-a3c6e1d46fc7@eisentraut.org>
 <dc8c8eab-9f7a-3189-4fd2-1ae1d50ac9b8@illuminatedcomputing.com>
From: Vik Fearing <vik@postgresfriends.org>
In-Reply-To: <dc8c8eab-9f7a-3189-4fd2-1ae1d50ac9b8@illuminatedcomputing.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/8a47be1e-4d12-4eb8-b3d6-90371a715ebc%40postgresfriends.org>
Precedence: bulk

On 10/11/23 05:47, Paul Jungwirth wrote:
>> +SELECT pg_get_indexdef(conindid, 0, true) FROM pg_constraint WHERE 
>> conname = 'temporal_rng_pk';
>> +                                pg_get_indexdef
>> +-------------------------------------------------------------------------------
>> + CREATE UNIQUE INDEX temporal_rng_pk ON temporal_rng USING gist (id, 
>> valid_at)
>>
>> Shouldn't this somehow show the operator classes for the columns?  We 
>> are using different operator classes for the id and valid_at columns, 
>> aren't we?
> 
> We only print the operator classes if they are not the default, so they 
> don't appear here.
> 
> I do suspect something more is desirable though. For exclusion 
> constraints we replace everything before the columns with just "EXCLUDE 
> USING gist". I could embed WITHOUT OVERLAPS but it's not valid syntax in 
> CREATE INDEX. Let me know if you have any ideas.

Why not?  The standard does not mention indexes (although some 
discussions last week might change that) so we can change the syntax for 
it as we wish.  Doing so would also allow us to use ALTER TABLE ... 
USING INDEX for such things.
-- 
Vik Fearing