Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1chOTJ-0000At-3w for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Feb 2017 22:36:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1chOTI-0008U1-01 for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Feb 2017 22:36:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1chORs-0006rD-1v for pgsql-hackers@postgresql.org; Fri, 24 Feb 2017 22:34:48 +0000 Received: from mail-qt0-x236.google.com ([2607:f8b0:400d:c0d::236]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1chORm-0006iz-Q6 for pgsql-hackers@postgresql.org; Fri, 24 Feb 2017 22:34:47 +0000 Received: by mail-qt0-x236.google.com with SMTP id r45so28119188qte.3 for ; Fri, 24 Feb 2017 14:34:42 -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=fooHs0owcq2lmljlEQAkDLkxphDk+L9Rml9Fy63LRSk=; b=Fw0DItQ5GItHBxI3zLRxPzXRZzh5ElJ+vuwk26yTln03h6yuKddGVh/IN4f8AEGBW1 DQlO5HbV95AF7l/MIkqIOcHwCpTRdaeQRUEtItouoawq5ioUZ6fTEfoOveuinlAGq1Xr Kn5+XOS+V/SQsEj4a5n1XGGl7zOTx53oVGDDfxo7D/JFGZGiHlTGkI+tqQrG6q5TSwCz hQzRm4BWsXX8e7wslBYeXxkPe6eOQo2ReaB5PCYMe9Tvn3RTg/zxEvakhPkfTdhZiYWr VKrtiOhtL9m0p5LvmxcKL2KgYOylS5MEC7VjTnwFyiMnDxmHpg3qo7hy/uBzPMSJr1X2 xzgQ== 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=fooHs0owcq2lmljlEQAkDLkxphDk+L9Rml9Fy63LRSk=; b=RgwL/7KMJuXoA7kquzDrHllB4c3S4a08KAB6Y38YBpWQb4Dk1yfguCkZ1VcNKzwnaQ KFPYS/CTJZvQH7VlZaOH2UO7Q7ZrAr88k5jk/GTwOEA0bmdNKsSX5oDROLGw0ulSwErq 5F4VACq0VElu40PHuYHYsMo6W5SjDRU9XAIqAIZ63duUjJ8z9nReDVxYGNjBAC4o5g7K uvb0xF6lkAD7oRO4JwcSYnJc4c0zMoqgRS11DviQfL7UNEz1bYPTNzCiZ6Fzn8eZnHz9 i7PqXjm1Rpfa3dr1f1rwZ7zrJTZA1yORrrihw9PN85INcIp4AuFIeKNgLrDg5ZLOMRPT IHjg== X-Gm-Message-State: AMke39nexfGJonDmrpGAA74oFvT432lKNOcyvOZSo6QG0u8Cqb5qZkD1abAn2chuPnE7EE0GfGnW1oupUKqxRZBfVTpyKVUh4q5FDDF5gNwdhyj3rnReXPW6ohuqSUClp/rHpJqyaeVrD1BtpY9/7Z147KKEKNd53JBeAYAQfHXF+Uxn8WhA3IDe82zCOWuMa8zq1ghzjnZTphI= X-Received: by 10.200.38.132 with SMTP id 4mr5311929qto.91.1487975680677; Fri, 24 Feb 2017 14:34:40 -0800 (PST) Received: from [192.168.10.146] ([98.122.164.227]) by smtp.gmail.com with ESMTPSA id 47sm5652422qtw.51.2017.02.24.14.34.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Feb 2017 14:34:40 -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> <4376a7bf-ab8c-e640-9021-94b148f9d733@2ndQuadrant.com> <6704.1487952174@sss.pgh.pa.us> <930cb563-6dc6-c4af-3be9-31f06c60361e@2ndQuadrant.com> Cc: PostgreSQL-development Message-ID: <8a8c60b4-39c0-69a4-824c-e364f5fd97ea@2ndQuadrant.com> Date: Fri, 24 Feb 2017 17:34:39 -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: <930cb563-6dc6-c4af-3be9-31f06c60361e@2ndQuadrant.com> 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/24/2017 02:55 PM, Andrew Dunstan wrote: > > On 02/24/2017 11:02 AM, Tom Lane wrote: >>> I don't know what to call it either. In my test I used >>> CallerContextFunctionCall2 - not sure if that's quite right, but should >>> be close. >> CallerInfo? CallerFInfo? Or we could spell out CallerFmgrInfo but >> that seems a bit verbose. >> >> > I'll go with CallerFInfoFunctionCall2 etc. > > In the btree_gist system the calls to the routines like enum_cmp are > buried about three levels deep. I'm thinking I'll just pass the flinfo > down the stack and just call these routines at the bottom level. > > > It's occurred to me that we could reduce the code clutter in fmgr.c a bit by turning the DirectFunctionCall{n]Coll functions into macros calling these functions and passing NULL as the flinfo param. 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