Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbYNH-0000j5-JS for pgsql-advocacy@arkaria.postgresql.org; Wed, 20 May 2020 23:43:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jbYNE-00025o-D2 for pgsql-advocacy@arkaria.postgresql.org; Wed, 20 May 2020 23:43:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbYNE-00025Q-7H for pgsql-advocacy@lists.postgresql.org; Wed, 20 May 2020 23:43:44 +0000 Received: from mail-qv1-xf43.google.com ([2607:f8b0:4864:20::f43]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jbYN6-0002L8-3T for pgsql-advocacy@lists.postgresql.org; Wed, 20 May 2020 23:43:42 +0000 Received: by mail-qv1-xf43.google.com with SMTP id x13so2283907qvr.2 for ; Wed, 20 May 2020 16:43:35 -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:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=KYPCw/46L6KzhyHZQkz+A6f5N7/khMvglhqkVxUw6iE=; b=AKNiTt4KGoURk/hZwZfp1wb1WGMr1jWFO78Qd278ROD0iLscbYdsgftLtLYp6jcI36 1SV/adIyqCoscfflU5msjjTJ/ZuutR3L2+mcGhkcIQm00fMhvriYQwJfsbcp+7ZHiCoy U3Q3JH+eJswG1esDlHD5LP7gJ2uzTQ/YUppdfydYZagxC3Dch25ai4UwMJC6SBLzsFW7 nEm4lHOB9nESC0P7QCGfZIg1VEeXJ9fp41dcbKMPyEzxgIm4sblzbcg4E09ZSdYv7wjR iSCaFcms2lL3QQApBgf6wEnxcIQsGIXYumjNLly9oo/yQc22CL5R/EjXsc0UlZxWxQdm Wzpg== 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:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=KYPCw/46L6KzhyHZQkz+A6f5N7/khMvglhqkVxUw6iE=; b=fSES9PXNCevrC8myfNVpJjsny9tu3GLNEWE6/COF3qtFQeMTAjJ4YBVmEtEvBAnwoh NxngB5pg454SMKa/wC0qoNA8jfMv+DMdzA2d97m67KehEsIClC+4YwWVaWqVsX/J3vcG pYgy7ak/2dfgIddakX/q9TvoVbabWeq3rGQ57ZrAsox36qHdmk8+ncdVhkxHqwh80tEy njjU6/ItdllLE0Hzb233C1PP7g2oae7yNsuYaZWlwXtslC34YcbMGBN1UIGzJh5roMdz DVQ+DiCTCh52VG0vF0BOdBowxL7PgK3gV1phfTfYBxkX7eM2DMnq2N6CQHv4SlpRMzoB 0d/w== X-Gm-Message-State: AOAM533r7wGA3eE5gv8x8HTGHI9XpVN7Q8fTixv/jAPMhOJAcDrW6NRb SGypk6vz7wHwxAuhdZLZSwU6g7olIOs/eTb9+rNHKUnWhC0O93bnG+NJieoNSalhqc4ZnQNmsMn 9MYXs78/OCMMOvJGxIwEkMQFT5ZcHQXaVBL1zAlbMxxXEYxVx3YJ+7y3AmUz4PbhtS5fZaIdR2c cGoYauPufZoZKwvMM6Tg== X-Google-Smtp-Source: ABdhPJwIHIrPqhZ6PRFeGCnRL6WmD7DnZfcyOJh/4SOi5RZ4imb7uPrIaL1ZOnkmC+ZEtlAHjdRyOA== X-Received: by 2002:a0c:ed4b:: with SMTP id v11mr7531374qvq.179.1590018213978; Wed, 20 May 2020 16:43:33 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id j11sm3180502qkk.33.2020.05.20.16.43.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 May 2020 16:43:33 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id A1E523005B2; Wed, 20 May 2020 19:43:31 -0400 (-04) Date: Wed, 20 May 2020 19:43:31 -0400 From: Alvaro Herrera To: "Jonathan S. Katz" Cc: PostgreSQL Advocacy Subject: Re: PostgreSQL 13 Beta 1 Release Announcement Draft Message-ID: <20200520234331.GA1103@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200520233018.GA32614@alvherre.pgsql> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-May-20, Alvaro Herrera wrote: > > PostgreSQL 13 adds incremental sorting, which accelerates sorting data when > > existing data in a query is already sorted. > > I'm not sure this is very accurate. I would say "incremental sorting, > which can take advantage of partially sorted data". (Could add more to > it, "when only a subset of the result set is needed", but that is > perhaps too many words). Rereading my suggestion, it's not super helpful either, as it suggests that it's useful when the data is sorted on disk. I'm coming up with "which can take advantage of sorted results from intermediate query steps to speed up subsequent query steps". Thanks -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services