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 1tNwvO-0038oX-Rv for pgsql-docs@arkaria.postgresql.org; Wed, 18 Dec 2024 16:29:27 +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 1tNwvN-00GePl-Fj for pgsql-docs@arkaria.postgresql.org; Wed, 18 Dec 2024 16:29:25 +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 1tNwvN-00GePc-7X for pgsql-docs@lists.postgresql.org; Wed, 18 Dec 2024 16:29:24 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tNwvK-000QzZ-7h for pgsql-docs@lists.postgresql.org; Wed, 18 Dec 2024 16:29:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4BIGTKHD2778774; Wed, 18 Dec 2024 11:29:20 -0500 From: Tom Lane To: sulfinu@gmail.com cc: pgsql-docs@lists.postgresql.org Subject: Re: Size limit for NOTIFY payload In-reply-to: References: Comments: In-reply-to sulfinu@gmail.com message dated "Mon, 16 Dec 2024 10:01:14 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2778772.1734539360.1@sss.pgh.pa.us> Date: Wed, 18 Dec 2024 11:29:20 -0500 Message-ID: <2778773.1734539360@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk sulfinu@gmail.com writes: > What's the character encoding of the NOTIFY payload, is it the default > database encoding? It's whatever encoding your database uses; NOTIFY doesn't do any transcoding. (We'd have to think harder about that if NOTIFY messages could cross database boundaries ... but they don't today.) regards, tom lane