Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ch1Df-0002mP-Ot for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Feb 2017 21:46:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ch1Df-0006wJ-AN for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Feb 2017 21:46:35 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ch1CD-0005FC-5h for pgsql-hackers@postgresql.org; Thu, 23 Feb 2017 21:45:05 +0000 Received: from mail-qk0-x231.google.com ([2607:f8b0:400d:c09::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ch1CA-0000Fg-DX for pgsql-hackers@postgresql.org; Thu, 23 Feb 2017 21:45:03 +0000 Received: by mail-qk0-x231.google.com with SMTP id s186so4122962qkb.1 for ; Thu, 23 Feb 2017 13:45:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=wi+NHpTJV6oTXCIQKbTHqqYeUeotIOx7sD43mvZAx70=; b=S3kHt0KCdEx4YjY2idkZcFGxmO/3O43RuBgWIECsm4fIvmmjFeXKPxVcV5HC6/Yqxl ixbgtrg49whcyiM1KOThMfva5NfKYUlE5v6F7RQcEQifgq5iErBqZDhHGEL2MucxjVyW gjFYhr159hb9D+/E0orjbwWIKqfZhZgXa7XrSdrN37YVQH2g/UmAnnnz3PLgWVw+nSiK GUdv73znY4UvgeQE2f3IGgHDNaZoLThOA1g+pVt9R/aXdtZVoHGIXF+jcbP2G/u7D79s 7pTvy3FbeBjjrJ0O1KcexNESrtfMmXE+p7Iap/quQPnFnxh1isolMqspOohxnPzjbcT6 LXWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=wi+NHpTJV6oTXCIQKbTHqqYeUeotIOx7sD43mvZAx70=; b=fjXOmiPfbApC5PTs0tWHQW6vnb+vEC+ZA94VHoaUQdwrNd8royHs0jgkaBhZER3wLQ zTS9sal8RULiuCiyXYXWXl7hqPuwRKKp8KmvZlbIz7GAy/JFwe44M+mQlLjaU66T8Ys1 dCyR6RnpZLzV9//rq7FwEJ9BadJiFNE2dubs+9X6yktQX8s+lIyLWB+/pzmmNoMnHC3u +M4QgJ+aV9zJhPB1Fu7RYJPCIUvryhjIXQwD1FKyyIkE8BfABmZ/GhThiwEcVG4yh4+K HP9EvxQ6u+HGD7l4YOIAEOuAWRUdEZ+Yj5InsfgAZMeb2Z/cv+HVDgJTFQHrF//I/U0d VIXQ== X-Gm-Message-State: AMke39m0TOyz1pQysDxxnFL9HjNH1s5oBMuby6rIm3UPJzTmTOLw0eisTYEspB461bMJS2605mMwerCWQ1TLFxeX4jTen6TqbZ2IvWQfGXd3hcUtptnjRgcgwKgz3A3L0hDTCGC+WEF/ydfN6ZWHF9uoYNHtxF+FC/CB2qNAWlKvMP+PpC1qCrFtEomyD5U7IKULY4Grl9z1Hj0= X-Received: by 10.55.43.213 with SMTP id r82mr44706648qkr.28.1487886301726; Thu, 23 Feb 2017 13:45:01 -0800 (PST) Received: from [192.168.10.146] ([98.122.164.227]) by smtp.gmail.com with ESMTPSA id z139sm3495368qkb.29.2017.02.23.13.45.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Feb 2017 13:45:01 -0800 (PST) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: btree_gin and btree_gist for enums To: Tom Lane References: <56EA8A71.8060107@dunslane.net> <56EACB8C.1040406@dunslane.net> <03f7d748-0f89-e8e1-094d-f04e1026b93d@dunslane.net> <27220.1478360811@sss.pgh.pa.us> <31412.1478366009@sss.pgh.pa.us> <60fb708c-8b3c-1337-934e-c1bfe2afc539@dunslane.net> <8258.1487886101@sss.pgh.pa.us> Cc: PostgreSQL-development Message-ID: <3b969375-dcb5-aa73-b8e9-cacd5c8d60ef@2ndQuadrant.com> Date: Thu, 23 Feb 2017 16:45:00 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <8258.1487886101@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 02/23/2017 04:41 PM, Tom Lane wrote: > BTW, while I'm looking at this ... isn't gin_enum_cmp broken on its face? > It's using DirectFunctionCall2 to call enum_cmp, and that's wrong because > DirectFunctionCall2 does not pass through a flinfo but enum_cmp needs to > have one. I've not tested, but I'm certain that this would dump core if > asked to compare odd-numbered enum OIDs. > > Yes, that's what I'm trying to fix. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers