Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VUREU-0003u3-Pv for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Oct 2013 01:09:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VUREU-0005bH-8m for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Oct 2013 01:09:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VURES-0005Zg-KT for pgsql-hackers@postgresql.org; Fri, 11 Oct 2013 01:09:32 +0000 Received: from mout.gmx.net ([212.227.17.20]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VUREP-0007Pc-KI for pgsql-hackers@postgresql.org; Fri, 11 Oct 2013 01:09:32 +0000 Received: from [10.0.0.5] ([67.165.8.132]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MN1Gu-1VSFNI1lgu-006hBf for ; Fri, 11 Oct 2013 03:09:28 +0200 Message-ID: <1381453766.5264.11.camel@vanquo.pezone.net> Subject: Re: GIN improvements part 1: additional information From: Peter Eisentraut To: Heikki Linnakangas Cc: Alexander Korotkov , pgsql-hackers Date: Thu, 10 Oct 2013 21:09:26 -0400 In-Reply-To: <52545362.4080806@vmware.com> References: <51CEA13C.8040103@vmware.com> <524E7C3B.7060402@vmware.com> <52545362.4080806@vmware.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-4+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:O+zGlonGnq5TybjijCDWFRzbYTQmt+0Z6FSjmTdT4c89DLUuJ3R e8MbGI8xHVcz5lP8C5EHOFTPHg6ZSYIoT38aV1O9etwC9TaDX3kl+XXkwMnq+Rb9czvfMmI NRxznbgoCDempTLnCjQP/h014+Ti0U26eVbIMyMQO6/8zy0VGwwhcPfFVfrt4MS8JP/cTap 4+FrkgCapq5aousYGsFqw== X-Pg-Spam-Score: -2.1 (--) 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 You linked to this email from the commitfest entry, but there is no patch here. You probably meant a different email. Check please. On Tue, 2013-10-08 at 21:48 +0300, Heikki Linnakangas wrote: > On 04.10.2013 14:13, Alexander Korotkov wrote: > > On Fri, Oct 4, 2013 at 12:28 PM, Heikki Linnakangas >> wrote: > > > >> In the attached patch, I in fact already did that for data leaf pages, but > >> didn't change the format of non-leaf pages yet. If we want to support > >> pg_upgrade, we might want to refrain from changing the non-leaf format. > > > > In GinDataLeafPageGetPostingList* you use sizeof(ItemPointerData) without > > MAXALIGN. Is it an error or you especially use 2 extra bytes on leaf page? > > I didn't even think of it. Now that I do think of it, I don't see a > reason to use MAXALIGN there. PostingItems only require 2-byte > alignment. It's a bit fragile and underdocumented though. It probably > would be good to have a struct to represent that layout. Something like: > > struct > { > ItemPointerData rightBound; > PostingItem postingItems[1]; /* variable length array */ > } PostingItemPageContent; > > And use that struct in the macros. > > Then again, we do currently use MAXALIGN there, so if we want to avoid > changing the on-disk format, we have to keep it... > > - Heikki > > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers