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 1hFihJ-0004qY-9W for pgsql-hackers@arkaria.postgresql.org; Sun, 14 Apr 2019 17:13:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hFigJ-0002PB-V4 for pgsql-hackers@arkaria.postgresql.org; Sun, 14 Apr 2019 17:12:39 +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 1hFigJ-000287-J7 for pgsql-hackers@lists.postgresql.org; Sun, 14 Apr 2019 17:12:39 +0000 Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hFigG-0001WD-Qf for pgsql-hackers@postgresql.org; Sun, 14 Apr 2019 17:12:39 +0000 Received: by mail-wm1-x334.google.com with SMTP id z24so17267619wmi.5 for ; Sun, 14 Apr 2019 10:12:36 -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=UXOJjuckZHutJaF7zysFkCx5CEtzoTnbIIS+xvScfHM=; b=uSd9qI3ycUv1XnBEz3XA4+YIb1cHBx31wSbfS31/CZ+I8PZBxvjv4AVKYUJmJi8uQt 5HsPLrpOFqAvBRhEw55WE9Dp5JHXg39aD3Zo/ldxtU4WYD5XM4ajpjw2aIj4qi/dExq8 fu86NPrfOUbKSB+b0lehypmYmGJZSA/2SByqilAXcFUY0Pxs/3P414iChjIVeg7YMtYD UNqaStKD9d1v24bajgGFw+fpx7yR/Z6lY5ZJyhrg2jgkVY4Zbyqiqf5VRAMhZl/3wdW7 8xAj3n4/uXDdR+APvJ/c43YJhxNv4/dYiRPmV821sHJXqWHB8B60QG0/ro6TRiJWV+hT Cglw== 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=UXOJjuckZHutJaF7zysFkCx5CEtzoTnbIIS+xvScfHM=; b=EHI83G8qO2Fy/njb7LBOGJqhh5jla6PJnpDsLf2gw8aqJvWTOVt8u6nI0tuVnBle5n eifjeL2n3XelAPhxk8jvPJ3nJWtcmcXNw5Zj4+i1ttHJ9hmNJFcK3Sc7nfnvvvCxfvO1 o5cLaPBp4yYXbfAxWdXRyamEyRKOivTqQNYlP4uNixrhp8mzu7hb9VSioj/eS9k+BPoe vBLAdIZZM8Jc8SplHt9kn7V9hRMQeWalkP+AYBj6wOYXSsr16T4jE9aPzhFempI1MM9M WwE6oGcsCW0CryS1pcMWPJi1cvRSXsMj5elUh5cKJBO5neupznKUVL9Zsq1BNvvlUHYC A7jQ== X-Gm-Message-State: APjAAAV3b5SKMCwO9aOhEZY7hSZcGB/woHa+0VE4wjiqgUjd/K6091ms sSM3GV2VU78E8AhoUKbwKHST6g== X-Google-Smtp-Source: APXvYqzdJmd89AQH890+s1xkOM14GDYJuzW41lR5jYE5yJ68UxEkSLbjicKGzcBtjTKl6qy6rb22kA== X-Received: by 2002:a1c:4d12:: with SMTP id o18mr17838322wmh.81.1555261955697; Sun, 14 Apr 2019 10:12:35 -0700 (PDT) Received: from localhost (ip-86-49-243-43.net.upcbroadband.cz. [86.49.243.43]) by smtp.gmail.com with ESMTPSA id t14sm11419936wmi.16.2019.04.14.10.12.34 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 14 Apr 2019 10:12:35 -0700 (PDT) Date: Sun, 14 Apr 2019 19:12:33 +0200 From: Tomas Vondra To: Andres Freund Cc: Konstantin Knizhnik , Andreas Karlsson , Ashwin Agrawal , Mark Kirkwood , PostgreSQL mailing lists Subject: Re: Zedstore - compressed in-core columnar storage Message-ID: <20190414171233.vhukbvlfwnacc37u@development> References: <6A2B85A8-1ABD-4F85-981E-C94172D662FD@pivotal.io> <44cafbdf-0a04-64ef-3cf8-6d5b14b68643@postgrespro.ru> <93222d26-2141-acf2-61ef-3127f57e80e6@proxel.se> <59ef6173-6667-8a02-ff7c-a52c8ce05a4f@postgrespro.ru> <20190414163618.x2bhtfwdulhah7o5@development> <20190414164510.idlavfnqkutj2h3u@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190414164510.idlavfnqkutj2h3u@alap3.anarazel.de> User-Agent: NeoMutt/20180716-1444-295967 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Apr 14, 2019 at 09:45:10AM -0700, Andres Freund wrote: >Hi, > >On 2019-04-14 18:36:18 +0200, Tomas Vondra wrote: >> I think those comparisons are cute and we did a fair amount of them when >> considering a drop-in replacement for pglz, but ultimately it might be a >> bit pointless because: >> >> (a) it very much depends on the dataset (one algorithm may work great on >> one type of data, suck on another) >> >> (b) different systems may require different trade-offs (high ingestion >> rate vs. best compression ratio) >> >> (c) decompression speed may be much more important >> >> What I'm trying to say is that we shouldn't obsess about picking one >> particular algorithm too much, because it's entirely pointless. Instead, >> we should probably design the system to support different compression >> algorithms, ideally at column level. > >I think we still need to pick a default algorithm, and realistically >that's going to be used by like 95% of the users. > True. Do you expect it to be specific to the column store, or should be set per-instance default (even for regular heap)? FWIW I think the conclusion from past dev meetings was we're unlikely to find anything better than lz4. I doubt that changed very much. regard -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services