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 1sHHt4-005cAB-TY for pgsql-general@arkaria.postgresql.org; Wed, 12 Jun 2024 06:55:15 +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 1sHHs5-00E6KO-0q for pgsql-general@arkaria.postgresql.org; Wed, 12 Jun 2024 06:54:13 +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 1sHHs4-00E6KF-LL for pgsql-general@lists.postgresql.org; Wed, 12 Jun 2024 06:54:13 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHHrz-000ute-0n for pgsql-general@lists.postgresql.org; Wed, 12 Jun 2024 06:54:12 +0000 Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-5b970a97e8eso3578138eaf.1 for ; Tue, 11 Jun 2024 23:54:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718175246; x=1718780046; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1qA4UD2phz5TvSgSnxfw36T32kkh20tlcXR164RztI4=; b=PaXhsCvQp/I8s7ycFPFcHxjW6ySveyTHJ5Zd0JvFRibjs6iCV/Fw1iDSmx3BeOe2Rb MmCkiho8HvAxSfz62XpFenQqXnYqVAvFRC9WyzoerXB8qDJqVEqgsp7FMnj0Yrax4Bkd NjB5OLrIpmLOuAbBsGF1VjMB4qhhKagsW0zsg87qYRibGdPcFhCVrP4yxmn0kHaCB4Mu pSh8y3rdbG3+XZuu6O4tazsiU8rfZ6tr2UXMlgsj0A+c3dD4bV42CSu4Zll7oE5iElc/ TExT1lGLjijulAp//jOssXHHH42cbzqmhcOQ1WjjS7/x/AGofbEKn31HVCBU+S6QAWAx w1EA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718175246; x=1718780046; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1qA4UD2phz5TvSgSnxfw36T32kkh20tlcXR164RztI4=; b=v1WvT26oI8fGvvF+aA9IFaUITtd9ok5VGPf9tWDDiJsIvo1tDBgQ0ZzjSU29JZOBfU 1AKU1McJHCXz9CmlZS95uXu5FOfERw9teJzWhW+K8eJ1dMCKMawGb6TF5p0PskkqwkP4 VfGbLfDV5nPhuVqpNVG77K33O3soJyp+3QCgaATQTrAXMwCMvRcZW7AeKTXuFpzPGoOp rgZZhzAZYZtOzvyjPJ3YU0okkJVCwzaHfm1aDANyXT4BPjM6oQS+Kjx5kCLm8YHg7MHf IRhWGOiEzVMySde87OsAeqyEfVa6e7qzJP/k2OrY554dkdGC7qSj34ayGTYZm8tISlxZ XhbQ== X-Gm-Message-State: AOJu0YwBoQAVTe5NY807e6LdXXiJ33Lxq1eMhjy5XeH15fOBlBQrw0PV YlGVs1xbqBZC7CpNtHZd871o0HqmwxSbq7a7B7AimeJ2LIPcDvl/PwOy5S6PsMTEbEvcebzVSjp /FJAJ55BVymz3LhBspZ1YiiUPHOE= X-Google-Smtp-Source: AGHT+IExvbXw+8wWURrRhZSCkGTYh977myiP9PhnzHCTsOzEhqhmZ5m0tkQteMDroGB7tjVfmP2fw/MNVGhDBIaFZZ0= X-Received: by 2002:a05:6871:799f:b0:254:b6f2:de84 with SMTP id 586e51a60fabf-25514e3a901mr1016135fac.41.1718175246130; Tue, 11 Jun 2024 23:54:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dominique Devienne Date: Wed, 12 Jun 2024 08:53:55 +0200 Message-ID: Subject: Re: Unexpected Backend PID reported by Notification To: "David G. Johnston" Cc: "pgsql-general@lists.postgresql.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Jun 11, 2024 at 5:29=E2=80=AFPM David G. Johnston wrote: > On Tuesday, June 11, 2024, Dominique Devienne wrote= : >> Are Stored PROCs running in a different backend? >> Are Triggers running in a different backend? > No to both. Whatever backend the SQL to invoke those was sent on is the = backend that executes them. Thanks for confirming David (and Adrian). I indeed had two connections after all. User error. Sorry for the noise. --DD