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 1szRor-0065NR-Nm for pgsql-general@arkaria.postgresql.org; Sat, 12 Oct 2024 02:25:25 +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 1szRop-00GOsE-63 for pgsql-general@arkaria.postgresql.org; Sat, 12 Oct 2024 02:25:23 +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 1szRoo-00GOrL-PN for pgsql-general@lists.postgresql.org; Sat, 12 Oct 2024 02:25:23 +0000 Received: from sender4-op-o15.zoho.com ([136.143.188.15]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szRol-000SDz-H4 for pgsql-general@lists.postgresql.org; Sat, 12 Oct 2024 02:25:21 +0000 ARC-Seal: i=1; a=rsa-sha256; t=1728699911; cv=none; d=zohomail.com; s=zohoarc; b=N45rkamt/XBbJcRRK7L3E3nXOAgbTejImTUoqyEEixU0ocueivzCoukHOC+j40D6MVBSf0Tqvk9zioNmxWTW/BKTmP1+fhloHirK2Zn8KYoCSPXWAfh0VMK27sPNT7tHoO1/ORPFJxYgNpDrIbHJoXZcr6wUJJ/dAFMPzodkluY= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1728699911; h=Content-Type:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=Co/osfXFCz7BXdFop963GB+vHDr1WUERlB0MYyWGnZo=; b=OJhDU09+s/7I9BL/DH5WOABywIVbiZ95O40ueGhRh1JTeTk7UWN+Z/3AbXDOXWwGQDkVHXOm5mq1WD8bfBhXkr61K8S0paEsij4CMyYW+OWCv5dsqqb8h1Ym5su/NF4LXdlzgUqZ3H1DfZqWPuEFzzlLJOyExQVOOXGkysSb+a8= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=iseki.space; spf=pass smtp.mailfrom=admin@iseki.space; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1728699911; s=zoho; d=iseki.space; i=admin@iseki.space; h=Content-Type:Message-ID:Date:Date:MIME-Version:Subject:Subject:To:To:Cc:Cc:References:From:From:In-Reply-To:Message-Id:Reply-To; bh=Co/osfXFCz7BXdFop963GB+vHDr1WUERlB0MYyWGnZo=; b=gEOzaPTBvwl4KZO5Mr4jB4QL9SUUkGOorxU1VcqLUV3NzMru1c9WRLeIAhbRjSlP G1/FGsv4L68lBteZVGzB3indec3K5bdSp/1FoffARwYUb3W8pwNMv058so7F+CVxRtz 472zJJ99Kjj4MqQFU1Q8ll0IpJqDTUTU6+b/4fT8= Received: by mx.zohomail.com with SMTPS id 1728699909453321.647131389112; Fri, 11 Oct 2024 19:25:09 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------T13ZXkKP9GAAYYHhyEI8hDTM" Message-ID: <32ae50a3-b6a3-4ca2-8051-9b0261ac430b@iseki.space> Date: Sat, 12 Oct 2024 10:25:08 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Questions about document "Concurrenry control" section To: Tom Lane , Erik Wienhold Cc: pgsql-general@lists.postgresql.org References: <7901c7e4-69c6-4bb2-8e9d-ad556d493717@iseki.space> <35d3e799d47700dc217b1f211aa0e0d5f4de4e67.camel@cybertec.at> <7d36a2bd-3aae-4785-b8b3-ab14cca8fdc0@iseki.space> <2852693.1728656353@sss.pgh.pa.us> From: iseki zero In-Reply-To: <2852693.1728656353@sss.pgh.pa.us> X-ZohoMailClient: External List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------T13ZXkKP9GAAYYHhyEI8hDTM Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit So, should I use the [reply to all] button? I'm afraid the receipt list will growing to have too many address. BTW, I'm using Thunderbird. If you have better software, tell me please. Sorry for my poor English. iseki zero. 在 2024/10/11 22:19, Tom Lane 写道: > Erik Wienhold writes: >> On 2024-10-11 15:00 +0200, iseki wrote: >>> 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? > It's been done in the past, but current practice is strongly against > it. For example, in your own message that I'm replying to, there's > a DKIM signature (RFC 6376): > > 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== > > That lists "reply-to" as one of the signed header fields. So if the > mailing list were to modify Reply-To (including inserting one where > there was none before) a DKIM-verifying recipient would regard the > message as a forgery. > > regards, tom lane > > --------------T13ZXkKP9GAAYYHhyEI8hDTM Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

So, should I use the [reply to all] button? I'm afraid the receipt list will growing to have too many address.

BTW, I'm using Thunderbird. If you have better software, tell me please.

Sorry for my poor English.

iseki zero.

在 2024/10/11 22:19, Tom Lane 写道:
Erik Wienhold <ewie@ewie.name> writes:
On 2024-10-11 15:00 +0200, iseki wrote:
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?
It's been done in the past, but current practice is strongly against
it.  For example, in your own message that I'm replying to, there's
a DKIM signature (RFC 6376):

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==

That lists "reply-to" as one of the signed header fields.  So if the
mailing list were to modify Reply-To (including inserting one where
there was none before) a DKIM-verifying recipient would regard the
message as a forgery.

			regards, tom lane


--------------T13ZXkKP9GAAYYHhyEI8hDTM--