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 1qcxJv-001gU0-M1 for pgsql-general@arkaria.postgresql.org; Mon, 04 Sep 2023 00:19:59 +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 1qcxJt-0073Qd-Hu for pgsql-general@arkaria.postgresql.org; Mon, 04 Sep 2023 00:19:57 +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 1qcxJt-0073QL-6Y for pgsql-general@lists.postgresql.org; Mon, 04 Sep 2023 00:19:56 +0000 Received: from mail-qt1-x829.google.com ([2607:f8b0:4864:20::829]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qcxJq-002aY8-B3 for pgsql-general@lists.postgresql.org; Mon, 04 Sep 2023 00:19:55 +0000 Received: by mail-qt1-x829.google.com with SMTP id d75a77b69052e-414a929a6f9so4536321cf.2 for ; Sun, 03 Sep 2023 17:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693786793; x=1694391593; darn=lists.postgresql.org; h=in-reply-to:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:from:to:cc:subject:date :message-id:reply-to; bh=rK0NYzgY/jyn4ctk65tjzQzvwaLXJ2oglfxih8jgw7g=; b=o0hm70CapQLuTolNddChWosuf0NcnCaKZuKhT0YXcZF4B7rVfI7PQXjsmSBQ06OEL3 H6ntyb5eWffK4BcD8JIpACiynzwUEWtX9sKEDqBe0irD1heLSt0pqNjVM3y7mYL4eNRN JijROhuzJzu+LPpP5YiJWJpEJZqQDWmFYcHnK4OetXTZSe+yHzGtIR07E1ltBlpaWUsU t0c6sXlzZd2PvxQBUg8TGgojuIUL3kQh4H2DZNF77Ilb2NL9QQqjnAp019sFKHDaMVoR OW8rFCLFSlQ77sWHkRPZTELC7iQfuwSCRlXLav3T6WXa16jElV14i5ZTbqljtDJSS1vf 1rPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693786793; x=1694391593; h=in-reply-to:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=rK0NYzgY/jyn4ctk65tjzQzvwaLXJ2oglfxih8jgw7g=; b=Alx8EMwax3BJmfMD9SGpZNoOg731hkGyVBoZ4JU6KQsxeg9/o2pA94N+QCO0y85tLV FIB7i7lSHWQj+DSfE2eNiUxt9o7OM/TJGKwWqGHPvkP1JGEUctJzbhuJZDwTPl7bmO7d W98MNDd94x+cWQ6YeDpguQDWNhutsqEGtPcr0cbgTWyYRC6gSGjo5os1230ScMb5FCHP 1ussg3pzqeU6oEP1csvyA1W8IIZOH1XXuC+Layo4KZhhf0GdzL0nRTOhkMOptRUWO1W4 Enszp6SGlR/I+eNmzrSmDQ5S1CVL+yr6HEoAq87OeraNvQ+sr2Jw9qnghK4mJFxFPeB1 YMLA== X-Gm-Message-State: AOJu0YwJSY9aWQLjDfk7rogFC0ETRoy6iY/6DnCXrCinuIjOhMKw/eyB j9HXtORNPHFmmQ0EoE7T1mjy21GzP4E= X-Google-Smtp-Source: AGHT+IGHFBn5kFUNylglL39kx+U74Drd6AXn44vT81GT6ceQc+IaO+OxLzmp0mwDCyv6G8krlkgnoA== X-Received: by 2002:ac8:5994:0:b0:410:a249:bee6 with SMTP id e20-20020ac85994000000b00410a249bee6mr9750809qte.14.1693786793215; Sun, 03 Sep 2023 17:19:53 -0700 (PDT) Received: from [192.168.2.170] ([67.70.150.114]) by smtp.gmail.com with ESMTPSA id ge20-20020a05622a5c9400b00407906a4c6fsm3196320qtb.71.2023.09.03.17.19.52 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 03 Sep 2023 17:19:52 -0700 (PDT) From: Amn Ojee Uw X-Google-Original-From: Amn Ojee Uw Content-Type: multipart/alternative; boundary="------------AIKWbaIAgjqeOC1SVp6VhLmD" Message-ID: <5dc2926b-32d6-dce7-49e6-aee508ce73c3@gmail.com> Date: Sun, 3 Sep 2023 20:19:44 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: PSQL = Yes ... JDBC = no ?? Content-Language: en-CA, es-ES To: pgsql-general@lists.postgresql.org References: <9524571e-96ed-15f0-4f70-89d9bbe273b9@aklaver.com> In-Reply-To: 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. --------------AIKWbaIAgjqeOC1SVp6VhLmD Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I see now, any suggestions as work around in JDBC? Thanks!! On 9/3/23 8:12 p.m., David G. Johnston wrote: > On Sunday, September 3, 2023, Amn Ojee Uw wrote: > > Are you saying that JDBC cannot handle or process \gexec, since it > is PG-15 exclusive? > > > psql is a client application present in all versions of PostgreSQL.  > It has a bunch of features related to executing SQL queries.  The > stuff that it is documented to do are only doable by it in many cases, > and in all cases are done locally, not by the server.  You cannot send > those meta-commands to the server, it has no clue what to do with > them.  And since you are using JDBC you by definition aren’t using psql. > > David J. > --------------AIKWbaIAgjqeOC1SVp6VhLmD Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

I see now, any suggestions as work around in JDBC?

Thanks!!

On 9/3/23 8:12 p.m., David G. Johnston wrote:
On Sunday, September 3, 2023, Amn Ojee Uw <amnojeeuw@gmail.com> wrote:

Are you saying that JDBC cannot handle or process \gexec, since it is PG-15 exclusive?


psql is a client application present in all versions of PostgreSQL.  It has a bunch of features related to executing SQL queries.  The stuff that it is documented to do are only doable by it in many cases, and in all cases are done locally, not by the server.  You cannot send those meta-commands to the server, it has no clue what to do with them.  And since you are using JDBC you by definition aren’t using psql.

David J.

--------------AIKWbaIAgjqeOC1SVp6VhLmD--