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 1nPloG-00080B-5D for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Mar 2022 13:48:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nPloE-0002YI-Vx for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Mar 2022 13:47:58 +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 1nPloE-0002Xn-Ll for pgsql-hackers@lists.postgresql.org; Thu, 03 Mar 2022 13:47:58 +0000 Received: from mail-yw1-x112e.google.com ([2607:f8b0:4864:20::112e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nPloC-0005qH-2W for pgsql-hackers@lists.postgresql.org; Thu, 03 Mar 2022 13:47:58 +0000 Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-2dbd8777564so56450367b3.0 for ; Thu, 03 Mar 2022 05:47:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OcsACxQ1mZkn4iCDeAIPNNYR/2VXtQCFASSmfy8WoDc=; b=Rick5cvgHzzOvx6jdLRYsj6TmIVzjhXSPvJRs+E1w8W3hSNUqsETMAUI4/C6yXcufP /o60ULzEl1u0u1oUpo6Zqlrj+K4pebLDImOYtVjQbvFAmv/SaVnSXsvhHhLHiixk7Gcl FXRvgzZdjQDtzi5dZfHJTJ6MgoqTFijTQTwobwBtpXebxzFloFfEcpvgouDIZ8TXq7jQ 5OU7sKmkN+PfUmEnGY8lho04Yy6nXThymaCyEbcamXiL9uLih9lkcoIks9qEM5JVrj3y wNPtpSSRDkL1ytbwDJNOOxZwiJ6Kw2SRx+s+nMGy49HEKmvTolfyiLt5UKMvegezlBlE +0dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OcsACxQ1mZkn4iCDeAIPNNYR/2VXtQCFASSmfy8WoDc=; b=0P/8Ufv0tOmfLBigfVRhzVD3Ek6uoXKHUk+UdE55qYiP2B8TNDk1DoTGEfa1ZDsEyE 1kLCf1PgDwD2hgMgHWtBSVqGr1U8wJpu9x4QQ0mKXDD4G0w8FpElRaZEWh2uEiuDDaJp mllq0VA2R1fFUpyQZeEnNfkulp/djMxJ+6uJMbd9wxn9DVzozy7sZkMHyWOIPtFw8M6r JVdm+j0bJN7ikIVMAQ0j/pO2TEqJNVzk1cFIG0RdlVIrl/A0Qt/zKsJ1FRxteGAb+4oI HMneipzWKgdSgPdOJYj8PRlQY/F6SyJv1bDBaPuSSO/hIb5lPpm2UvcfGl94qDp0TNCc 8Ysg== X-Gm-Message-State: AOAM531qBbLOaH1P0upuTtF+kKUTgJ5ZsVlLgU9wGV9rnaioU24MXvhp jtlJGMNzEL+odzvyIixzvCp8BsvhWOocYNgpgsu7ZQMRq+0= X-Google-Smtp-Source: ABdhPJwnmEcdprZe+ccgfN9eIrPSa4BugWpxe6x+eUsLA1LvTGepE+h7M4v3rMTLVV1OnTnfLb/19twuR7UVVfkt4CU= X-Received: by 2002:a81:e105:0:b0:2d0:6b27:2009 with SMTP id w5-20020a81e105000000b002d06b272009mr36207842ywh.462.1646315274434; Thu, 03 Mar 2022 05:47:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Pavel Borisov Date: Thu, 3 Mar 2022 17:47:43 +0400 Message-ID: Subject: Re: Problem with moderation of messages with patched attached. To: Dave Page Cc: Postgres hackers Content-Type: multipart/alternative; boundary="0000000000001efb8505d950a53d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001efb8505d950a53d Content-Type: text/plain; charset="UTF-8" > > On Thu, 3 Mar 2022 at 13:28, Pavel Borisov wrote: > >> The mail system doesn't have the capability to apply different moderation >>> rules for people in that way I'm afraid. >>> >> Maybe then 2MB for everyone? Otherwise it's not so convenient. Lead to >> answers before the questions in the thread [1], seems weird. >> > > Then someone will complain if their patch is 2.1MB! How often are messages > legitimately over 1MB anyway, even with a patch? I don't usually moderate > -hackers, so I don't know if this is a common thing or not. > Hi, Dave! Authors in the mentioned thread [1] bump into this issue while posting all 11 versions of a patchset. It is little bit more than 1MB. We can try to use .gz and if this doesn't work we report it again. I'll ping a message across to the sysadmin team anyway; I can't just change > that setting without buy-in from the rest of the team. > Thanks! Maybe this will solve the issue. [1] https://www.postgresql.org/message-id/flat/CACG%3DezZe1NQSCnfHOr78AtAZxJZeCvxrts0ygrxYwe%3DpyyjVWA%40mail.gmail.com -- Best regards, Pavel Borisov Postgres Professional: http://postgrespro.com --0000000000001efb8505d950a53d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, 3 Mar 2022 at 13:28, Pavel Borisov <pashkin.elfe@gmai= l.com> wrote:
Th= e mail system doesn't have the capability to apply different moderation= rules for people in that way I'm afraid.
Maybe then 2MB for everyone? Otherwise it's not so convenient. Le= ad to answers before the questions in the thread=C2=A0[1], seems weird.
Then someone will complain if their patch is 2.1MB! How often a= re messages legitimately over 1MB anyway, even with a patch? I don't us= ually moderate -hackers, so I don't know if this is a common thing or n= ot.
Hi, Dave!
Authors in the m= entioned thread [1] bump into this issue while posting all 11 versions of a= patchset. It is little=C2=A0bit more than 1MB. We can try to use .gz and i= f this doesn't work we report it again.

I'll ping a message across to the sysadmin team anyway; I = can't just change that setting without buy-in from the rest of the team= .
Thanks! Maybe this will solve the issu= e.=C2=A0

--
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com
--0000000000001efb8505d950a53d--