Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iFJbM-0000K1-8F for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Oct 2019 14:58:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iFJbL-0003pe-0W for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Oct 2019 14:58:07 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1iFJbK-0003pS-NM for pgsql-hackers@lists.postgresql.org; Tue, 01 Oct 2019 14:58:06 +0000 Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iFJbH-0007G4-Q8 for pgsql-hackers@postgresql.org; Tue, 01 Oct 2019 14:58:06 +0000 Received: by mail-wm1-x341.google.com with SMTP id 7so3774928wme.1 for ; Tue, 01 Oct 2019 07:58:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=bgArACVpFQahWjbWIGbqvUC7HwNde4EVl9lgNAp8oxs=; b=MP06pZnZTXNXhWxTQ5GlIAwz06S+J0fWJXocoq3uryv2JXib6GddWajyBtz+OwE7Sj bdz/nb1m18BCBUU9hBajQ0Ox18n6+7XmSE8Ner06Xx6GVMN7YIkHrQufZaYEczTHsL+w mDpZPNDvAIv4ury+ZmjeZiYtPYvC9Bz6y1DUbv2+vo2P8lG0sUYKqA3EYdcnW54Wc3jK XOml9LGvt7nN1CM0DQ3dqnV3Wr+eqRjqddp8GPfRIvw/PueISHHSdubpPJtuYEcxuxVa gpD2uQS/D12erKEk/m8c2aDcHKmcOpcsQM/NyQof37rpzmr7XgYVfX31Ia1c6S5LcafC 86aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=bgArACVpFQahWjbWIGbqvUC7HwNde4EVl9lgNAp8oxs=; b=tQZa9PQkPBWsgIQHl52RUZ9vtbkbz1tv22di3r8Azm42UMmJDQnM6iHFpOorn+PDXc Pc63H2R0xvXOmPrQdFKLwsKs7jOwz2ZKeH2ZbziKge575wNOP9KjzfvKW0uD0kQWskCs NF0xg+euLW45WsMuNLjS1kRLOnTjFfXfnzjBx6dO/yF29vZ1YWyjDems3fqvGmyNsd6Q cPn+NK68D3U/qFHSGNdYzYM5cCgcZ1pKdEg6BkgY+PNYL6Q0T+qmwBzP32zLHCpH7kTZ MBTrAQfLv3ney5129mGH7iInLGZTSwOv20qv9N/PYJFHE/JsvaFxuYVUAadMty5QLqZ6 6ymg== X-Gm-Message-State: APjAAAUiFMyaHsbTrTQgogZpsp8WdX+Mfq4DhJP2xye30pu0nPitDdbX 1lEg+9hb+nfO4mqkg8Q/sngMcPTxmiw= X-Google-Smtp-Source: APXvYqztaDYv63jZDuiWdGC2NbiEWfq3tRgCwGv1ulih4nT9/6cLXVuc8h4mg/zprVoWvBbCJAmqAg== X-Received: by 2002:a1c:a8cb:: with SMTP id r194mr3984706wme.156.1569941882662; Tue, 01 Oct 2019 07:58:02 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id z125sm5424289wme.37.2019.10.01.07.58.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Oct 2019 07:58:00 -0700 (PDT) Date: Tue, 1 Oct 2019 16:57:58 +0200 From: Tomas Vondra To: Tom Lane Cc: Andrey Borodin , Alvaro Herrera , Binguo Bao , Paul Ramsey , Pgsql Hackers Subject: Re: Optimize partial TOAST decompression Message-ID: <20191001145758.rofbwvguwxwpdxyb@development> References: <20190925203834.GA25060@alvherre.pgsql> <20190926230036.ubxzgkqsphbzmbdl@development> <20190930155607.5tnyzksijgm4imbg@development> <20190930172951.gdedvexnf4d2wv5e@development> <123EF56B-F8EC-4868-B49B-095795095E7A@yandex-team.ru> <20191001100805.wnnuj73kuzfwzs56@development> <20191001123420.uwzxtqr7qvleyxef@development> <20191001131803.j6uin7nho7t6vxzy@development> <4411.1569939037@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4411.1569939037@sss.pgh.pa.us> User-Agent: NeoMutt/20180716 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Oct 01, 2019 at 10:10:37AM -0400, Tom Lane wrote: >Tomas Vondra writes: >> Hmmm, this seems to trigger a failure on thorntail, which is a sparc64 >> machine (and it seems to pass on all x86 machines, so far). > >gharial's not happy either, and I bet if you wait a bit longer you'll >see the same on other big-endian machines. > >> I wonder if that's wrong, somehow ... Maybe it should use VARSIZE_ANY, >> but then how would it work on any platform and only fail on sparc64? > >Maybe it accidentally seems to work on little-endian, thanks to the >different definitions of varlena headers? > Maybe. Let's see if just using VARSIZE_ANY does the trick. If not, I'll investigate further. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services