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 1szFz8-0056mv-9U for pgsql-general@arkaria.postgresql.org; Fri, 11 Oct 2024 13:47:14 +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 1szFz6-004nl7-Aa for pgsql-general@arkaria.postgresql.org; Fri, 11 Oct 2024 13:47:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szFz5-004nkN-So for pgsql-general@lists.postgresql.org; Fri, 11 Oct 2024 13:47:12 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szFyz-000NHE-Br for pgsql-general@lists.postgresql.org; Fri, 11 Oct 2024 13:47:11 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4XQ7GC0sZBz9sWK; Fri, 11 Oct 2024 15:46:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1728654419; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7w7CHebdKaXtlhCMxa/jNIcoEy1tFhZmzOD+dT7nP8k=; b=K3s//HzYXU+chTDeY5p/wGwd5eglESiaugVSpGWo49ryL9ajLdimYMD3uIc3rr8PglZizV nk2wDiMsHnLR0EAgKsGzNvtxt4N9hHxMk7UI3F4XOVYqnemk95YVRNpFpEFww833uUqA+9 RPypj/ezsKbi2vBzzXIoZ+Tf3t6XfuZYf6poq1J+ud0X278yQMnA1XbZNsenQkCWoYPiXb yklxY2Nbp9NyiDHCDQ0KPYAT6/0ttzbprNhgSzhN7LND6ehUvLlsmKG3rwqby2LmFRwliQ RDZ4MAxEzZKfOr8HGnubQf8FdQPGw6jlAn3U8199c+3QcIAWJ99Wrtb5rQPdEw== Date: Fri, 11 Oct 2024 15:46:56 +0200 From: Erik Wienhold To: iseki Cc: pgsql-general@lists.postgresql.org Subject: Re: Questions about document "Concurrenry control" section Message-ID: References: <7901c7e4-69c6-4bb2-8e9d-ad556d493717@iseki.space> <35d3e799d47700dc217b1f211aa0e0d5f4de4e67.camel@cybertec.at> <7d36a2bd-3aae-4785-b8b3-ab14cca8fdc0@iseki.space> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-10-11 15:00 +0200, iseki wrote: > Oh sorry, I should use [reply to all] instead of [reply]. I don't have much > experience with mailing lists... > > But why the mailing list haven't use the "Reply-To" header specify where to > reply? Because the mail is you send to me directly? The message author sets Reply-To, if necessary, according to RFC 5322. Are there mailing lists that actually set this header? -- Erik