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 1ujiFr-00B7RS-CK for pgsql-general@arkaria.postgresql.org; Wed, 06 Aug 2025 17:48:47 +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 1ujiFq-00HObe-Ba for pgsql-general@arkaria.postgresql.org; Wed, 06 Aug 2025 17:48:46 +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 1ujiFq-00HObQ-1K for pgsql-general@lists.postgresql.org; Wed, 06 Aug 2025 17:48:46 +0000 Received: from mail-ot1-x32e.google.com ([2607:f8b0:4864:20::32e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ujiFn-00153W-19 for pgsql-general@lists.postgresql.org; Wed, 06 Aug 2025 17:48:45 +0000 Received: by mail-ot1-x32e.google.com with SMTP id 46e09a7af769-741a905439eso154229a34.0 for ; Wed, 06 Aug 2025 10:48:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754502523; x=1755107323; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=EPXiX7kf3a6rwvhQShXzHcOfgOP4JVxTduQpizFZBLc=; b=g4vSkbT3RXDdt+ULBnj9zOagM7+FFAf4sp9EX4S24h8PLb2KS3KYYtmvUNTmTm6/R4 jouMX8OdAZScHuhQEstzDsKfrqvX6BGmXj4IfOcF5gcGeGSTUTJCkZOKZtySj9wOcT+b W1O7Bq3ntcoz1D9haz4Gb5udg7lYDVePC8t46WhPwqkEjtbg4E4tw2+k9P1ZXzFpE5JA SfHnVspXXRsZGOnS/q6ZKVGqU8Lx5pRqe4oM802Mxc1aMYKgMl7OVhC0t/rMcPGb4BMK Sc136+9sLSmMhmqBsyMtt8BYV7GErIgGjpebgj5aw/7uNFs97DXoSWveoIveOeAjeePU evhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754502523; x=1755107323; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=EPXiX7kf3a6rwvhQShXzHcOfgOP4JVxTduQpizFZBLc=; b=MJvrofIQBwuVvErBrXE4lK8AVWGUVacKO54AVzSCD48u/S33h7gbigWponSk4J/HrE I6VZwIO9AhMTvfcQqIHx0y+QmyYGbq4k5/v7XvUCa8eqx7SaAdxtCRLraOp00eQsoeHX 3TYdNHPHv5kXYzVQSW4xEEHJm4+e0o/ENKiiahfAI3biYcqT45Z9nnYFrx0dRVES5VhL UamamkxVjLDjR/Sp3HVTSVqw88SvVdn9SfJjJqHPPiSZ4z191gC6Hy9VrkUGceQqd22c oTNrzrSUk8Bu36PVsTI+xJyqPBtSgErjvkHanNZID+36eD+6YP4Kk2R1WK3gUum/7Nrn UmBQ== X-Gm-Message-State: AOJu0YyekbcgI0mumxoe+7Iv37xwMkYcq1LXbyiUiLfCP0DV0I1vck38 muIRtlM8MLa+XUeMhiaxZwMFbpdUU51LbZ9xkf/rg+a/VfzsaRz4yVwk20R705tblgSh2JW8s5y W0RdoKOTUKzogJqEx4RoBqqkhzMBMU4FJqkQs X-Gm-Gg: ASbGncuZU9427HO7cX3MLJZch1z3cIdcRN5drRWKe03PotRm5Q6kWlUdtkiV04K/SGt O7nxTQp7WAxL5aaUpFbXJaI6DDZaVfNjINnZR6fqfNEOSr8f1pmbfS/j5NuJtpZXkPuXWsW1zA8 ExN+apqMf8bwTqbX8ZoXmvNrQP+FMDnMtp0jdTgo8vVbPss+TYgrvA6XVjFGURs/BZvCnyz6rZt iPPNfHUcA== X-Google-Smtp-Source: AGHT+IGUp4uJHr6SOQGDhMcv8LokqzXs2C4gZFdmX1S/76enoE3rxePtwdBuoIXw9UgE4A9ILb9wcYqS1qoiu63GwMI= X-Received: by 2002:a05:6830:3486:b0:741:21b8:b24d with SMTP id 46e09a7af769-74308cfb1d9mr2324028a34.5.1754502523519; Wed, 06 Aug 2025 10:48:43 -0700 (PDT) MIME-Version: 1.0 From: Dominique Devienne Date: Wed, 6 Aug 2025 19:48:30 +0200 X-Gm-Features: Ac12FXyVUsaMA2pxbBbwt_XGfLYapQApWegb-a6x3AumRmKEH4no3FgGbGCc9S8 Message-ID: Subject: CALL and named parameters To: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk (sorry, this is a rant...). Was getting an error calling a procedure ERROR: procedure ... does not exist HINT: No procedure matches the given name and argument types. You might need to add explicit type casts. I verify USAGE on the SCHEMA of the proc. OK. I verify EXECUTE on the FUNCTION. OK. I verify the names of the parameters, in my CALL with named arguments. OK. Turns out, thanks to ChatGPT for clueing me in, CALL does NOT support named parameters. And it's about the least helpful error message PostgreSQL could have provided IMO. I'd expect something much better in this specific case, FWIW. That's two unhelpful error messages in a short time :). Thanks, and again sorry for the rant. Wasted time on this. --DD