Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUtYq-006VJl-9C for pgsql-hackers@arkaria.postgresql.org; Fri, 19 Jul 2024 19:46:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sUtYo-004lhj-5V for pgsql-hackers@arkaria.postgresql.org; Fri, 19 Jul 2024 19:46:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUtYn-004lhb-Rz for pgsql-hackers@lists.postgresql.org; Fri, 19 Jul 2024 19:46:34 +0000 Received: from mail-il1-x134.google.com ([2607:f8b0:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sUtYm-000QxJ-51 for pgsql-hackers@lists.postgresql.org; Fri, 19 Jul 2024 19:46:33 +0000 Received: by mail-il1-x134.google.com with SMTP id e9e14a558f8ab-37636c3872bso9937605ab.3 for ; Fri, 19 Jul 2024 12:46:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721418390; x=1722023190; darn=lists.postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=GxGkHgy7xegvxEGojiyRYZdVmCr4u1pc4FSycnlCfUY=; b=EhfWmVSyc0i9SZn9axgivO2ZY7lYmnZCMcak2vM0N0XEe0nmLG52SZvrL8+IHxRUrr vbmC5EGwBmIuaEYmAWrWSAh1DE3mnnDIrBgBySN3D/t0jPWEKea8oqgTOKdeY3V623eI dbXAvQB+Vcx6/U8YJGDiIgCN7RQuaCMmzWUE/d1R7HL1pJh+juhIBdwSH/s9tHrcrKss tCz1o09GFr84nNRyVcVLYZU2KoOZvzWKosSfLF+sfZwDfqx23TWmPnOqh4xV2MiHH3nv blHzlRKUHEkAc2/RdIwK09iHLBzupUTvivP0ia/xLXb+IFDVzvGraCFnEW0+Pppp+KZZ cUcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721418390; x=1722023190; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=GxGkHgy7xegvxEGojiyRYZdVmCr4u1pc4FSycnlCfUY=; b=QQb5alkE5JTCdR8Soxy8YEb6hpdLf9jpSZpUzpUPJdsSntWdmwjJ3Mrn80VLnFrEb+ OeQ1HI4wcJVfNBuDoB1ej0DkeOY6BwTzAn07BLlm800ArzIobTCLUoYwwzQIX1tsnFKQ 3QU07+qlNGvSTkBA72Czhx2KY4kCKecJuRTB8E/YSE8AOd4gVJb1WcnMNstLWSk1V6Sp mTuLlPKnYZPNZSY1dxCWu1o5MB503d13wxPG3pIGVP3mk3bEf+tNyveWkedKps0uupGc iQrgXP1j6p+Nc0A6O+fxrAPDwLxlCdBpPZZ50Y3PJkOVPS2pemW3/P5HkrR594KZe3OX ai4A== X-Gm-Message-State: AOJu0YyG4F5y14ChpjLnyMzY5KRD9N+w6M6J7KmRXCqYyuhHOIelcSEU 0JnDhEF/l8naRgkRLata5cG7joPb8vvpIUBwe4y0WTWR9IXmFss3 X-Google-Smtp-Source: AGHT+IEeS7Pvbyh+OfgjiIuEl9gv6TLLMmlBJP7tDIf8VD0LFWi3z+joKJ1nPNaax2UHvloC2SwWSw== X-Received: by 2002:a05:6e02:18cc:b0:375:c473:4a78 with SMTP id e9e14a558f8ab-39557049140mr110317055ab.23.1721418390385; Fri, 19 Jul 2024 12:46:30 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-397f5a41b74sm6261045ab.31.2024.07.19.12.46.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Jul 2024 12:46:30 -0700 (PDT) Date: Fri, 19 Jul 2024 14:46:28 -0500 From: Nathan Bossart To: "David E. Wheeler" Cc: PostgreSQL Hackers Subject: Re: DSO Terms Galore Message-ID: References: <0B593F46-E673-49BC-A4F7-F27489655284@justatheory.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0B593F46-E673-49BC-A4F7-F27489655284@justatheory.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jul 19, 2024 at 03:27:49PM -0400, David E. Wheeler wrote: > I´m trying to understand the standard terms for extension libraries. > There seem too a bewildering number of terms used to refer to a shared > object library, for example: > > [...] > > What is the standard term for these things? Or perhaps, what *should* it > be? "Module"? "Library"? "Object"? "Shared ____"? "Dynamic ____"? > > Would it be useful to decide on one term (perhaps with "file" appended > where it refers to a file that contains one of these things) and > standardize the docs? The lack of consistent terminology seems at least potentially confusing for readers. My first reaction is that "shared library" is probably fine. -- nathan