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 1jJqn4-0000IP-4h for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Apr 2020 03:45:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jJqn2-0008SF-TT for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Apr 2020 03:45:12 +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 1jJqn2-0008R1-Li for pgsql-hackers@lists.postgresql.org; Thu, 02 Apr 2020 03:45:12 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jJqn0-0006Ep-Au for pgsql-hackers@postgresql.org; Thu, 02 Apr 2020 03:45:12 +0000 Received: by mail-ed1-x52d.google.com with SMTP id bd14so2425002edb.10 for ; Wed, 01 Apr 2020 20:45:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XQ9h1LEoFEWJXzzeCzVssH/2ZzqGlfhicxNvEP3lNXw=; b=tDVh1VTW4aNXITM3YptCgGNox8kF9GYKNC4rVGqdfI5UJ+sdWf8YyNkMJM11tAjzUM +ZX/7mmo4eGeoEzK1ngBAQfv6BVjEn6bsq+vuPMbdOOodCzNYVysmlTzw+1VZi97/d5i pOX51CVPVX43SfVne2ai7E6JfgBod7nTpemdVCvgqPuMODCvnx1M7g95WlHqjTQM7eW9 45P6yBXhw7iBmKot8ekclQRkgZKpYFOHM1q5802QFv/5JT9RbhZR1gYPlfVasloK0p2e l3lwnLF/psujowHTYhZqcI2Vtlw3H7592Yq6NudqUTjx57j/6aY3vPJNMRXKYpilHXkj noUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XQ9h1LEoFEWJXzzeCzVssH/2ZzqGlfhicxNvEP3lNXw=; b=LOl0msTqJRiNvFkWy8QfYau8dv6cUt9dYZ+thqLWvnc5l8sBetQGtN3mAUEJC0xqWl 2BDxR7GoGX4JzGr5ViVEt4ysLZnaPrwCw9X9ifgg8cInrvuF600NFRa32KYXjyxc9E2x imYVTV2W+naepbt2GXMK0DUyBd60SuSJEH7d6bLW84Cfjw8833uUlmm6fLK4MFGHKTVV NU0DlKHaYt+axrwEc+Hu8rbEa3402o4t52o1IiArbB+yrLi+noSH3sGN+tEAZRi1fzOE 9QbswiFuQv9znJXf9b21yfLqnSHNzm8w4aUco09TcT3sHG/9VjzpyW0BvjrhUBd7BpdV s74g== X-Gm-Message-State: AGi0PuYOWr2MNKa0QJtgKelSklRCFm0ikXuBZAosg0Mf7bBghzl+ZeH6 MVZWfk+VuHOUHGrK5tPkJk+7It3khmKTMqIRUmUNZD6o X-Google-Smtp-Source: APiQypJjzfzsUXLISA6lLu/0tLraGPFonQfCofMyKVEylvJAPLOLHzBEnAW29HxLIl+Yc3RLvN2KVPpt5JM5bW4WnbM= X-Received: by 2002:a17:906:f209:: with SMTP id gt9mr1281883ejb.124.1585799108617; Wed, 01 Apr 2020 20:45:08 -0700 (PDT) MIME-Version: 1.0 References: <20200402010934.GZ14618@telsasoft.com> <20200402014111.GA9466@alvherre.pgsql> In-Reply-To: <20200402014111.GA9466@alvherre.pgsql> From: Corey Huinker Date: Wed, 1 Apr 2020 23:44:56 -0400 Message-ID: Subject: Re: Add A Glossary To: Alvaro Herrera Cc: Justin Pryzby , pgsql-hackers@postgresql.org Content-Type: multipart/alternative; boundary="0000000000008dea8005a246a0fc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000008dea8005a246a0fc Content-Type: text/plain; charset="UTF-8" > > I propose we define "planner" and make "optimizer" a entry. > I have no objection to more entries, or edits to entries, but am concerned that the process leads to someone having to manually merge several start-from-scratch patches, with no clear sense of when we'll be done. I may make sense to appoint an edit-collector. > I further propose not to define the term "normalized", at least not for > now. That seems a very deep rabbit hole. > +1 I think we appointed a guy named Xeno to work on that definition. He says he's getting close... --0000000000008dea8005a246a0fc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I propose we define "planner" and make "optimizer" a &l= t;glosssee> entry.

I have no objecti= on to more entries, or edits to entries, but am concerned that the process = leads to someone having to manually merge several start-from-scratch patche= s, with no clear sense of when we'll be done. I may make sense to appoi= nt an edit-collector.
=C2=A0
I further propose not to define the term "normalized&q= uot;, at least not for
now.=C2=A0 That seems a very deep rabbit hole.

+1 I think we appointed a guy named Xeno to work on that definition= . He says he's getting close...
=C2=A0
--0000000000008dea8005a246a0fc--