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 1rx9TN-006fTw-Cr for pgsql-docs@arkaria.postgresql.org; Wed, 17 Apr 2024 17:53:29 +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 1rx9TL-00Disu-5h for pgsql-docs@arkaria.postgresql.org; Wed, 17 Apr 2024 17:53:27 +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 1rx9TK-00Disg-UO for pgsql-docs@lists.postgresql.org; Wed, 17 Apr 2024 17:53:26 +0000 Received: from mail-oo1-xc33.google.com ([2607:f8b0:4864:20::c33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rx9TI-003KTf-DL for pgsql-docs@lists.postgresql.org; Wed, 17 Apr 2024 17:53:25 +0000 Received: by mail-oo1-xc33.google.com with SMTP id 006d021491bc7-5aa17c29ba0so1197eaf.3 for ; Wed, 17 Apr 2024 10:53:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713376403; x=1713981203; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4sTHfT2kbEh3ldBGs+Cks7wnnLxLLH0Y2yVcF1Wn6Sw=; b=ewTm8SHnIpgjttFrIALLqXHPaN36gGrHbdxDDmAxqH8zeeBf7xocllL+7fzwRwZePb mWfRxJaimzQ424AYHf/jtBOh49tL1oUTkvbzb1abTFPt7LxklvKuIr8R1HzElgTKpF/f 9uXFjctHLMHPfXvkq7Nwu1eFHFOFijRsdCaBjJlPSG7gPmlm03LLu5JnGCQpnFDR5rqk i1LBLcII4jWQL9cF0hVSVQJFVUR+YAG2O+AyzD76B9ZyEQMNp5OW7xj2maRvxse8HE+9 yaeW0YBO1ZLczAJhxDOGjpT2Jp1SoQCn8GVADb4MpGMMNM7hhR3fCF/62q6/M2i8IwHv f6TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713376403; x=1713981203; h=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=4sTHfT2kbEh3ldBGs+Cks7wnnLxLLH0Y2yVcF1Wn6Sw=; b=Hi29C6hQDJb6CwP/i6iStT7W7V4xR/pSPPdE+u+as5/wxxKF9xO4hm87aCgJwgiToR jbxxltWOP/fjny9Mlcv5ciZfr2yfMeY/OJ2wSlVQw76/HMutJcUO4UXHnqmXSgPz/J8D l0vZVQw40j+8WmdRViuUhTP+LjyfZIKaZu/ZB7pbL3d0XPPIc3O/qxbUXtZuGt6aMc06 p/wqtpFKjUe/4O+IKcYViau/FKePs4Evpqz06pxSQQTMSxZ1nICMaZ6WssbzYeH57MrB O9kx3F2FiYEcxSvEGkNfiCUfMEBWpJCgOE6KfYRgdfsf1LZkocO3miwyz3iW6GsQfnOJ L+nw== X-Gm-Message-State: AOJu0YzQb0/hIE0wVaUpt93P/ieiCEJY1Bk3ZWfGIlq6zKCwnHhlmVCQ 7DYdBvoXXjEV2B26CLGhfGmIIlrJHO4+xUCjFzITZnynwd92B/HcPQ/4Xf0diuaCkXmZBoWN8zQ LLU4pTbpRNxuf8Lr5Tikk54VflRo= X-Google-Smtp-Source: AGHT+IHdGxwRQgxFnRjGYs6KQM5Ks5r9AK5n0qY3UVEITr68iBZxgqim9dUaG+hTLVd00CVjjJP4FTfxp6YCcWS96S4= X-Received: by 2002:a4a:4ec2:0:b0:5ac:c39b:3a7a with SMTP id r185-20020a4a4ec2000000b005acc39b3a7amr536845ooa.1.1713376403638; Wed, 17 Apr 2024 10:53:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kirk Wolak Date: Wed, 17 Apr 2024 13:52:57 -0400 Message-ID: Subject: Re: Update Help on PREPARE to mention DEALLOCATE To: "David G. Johnston" Cc: pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e7d11006164e8757" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e7d11006164e8757 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 16, 2024 at 4:42=E2=80=AFPM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Tue, Apr 16, 2024 at 1:27=E2=80=AFPM Kirk Wolak wro= te: > >> Could we make the PREPARE line read >> ... >> > No. That is a syntax excerpt and the prepare command doesn't accept an > optional deallocate keyword at that position. > > If we wanted to improve the psql help here we'd have two options: > Add to the description: > prepare a statement for execution (undo this with Deallocate) > I am 100% okay with that. I would consider DEALLOCATE to be caps so it looks like a command. But would leave that to you guys... Great observations on the other issues. Not looking to complicate things. Just enough bread crumbs to link things. Thanks! --000000000000e7d11006164e8757 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Apr 16, 2024 at 4:42=E2=80=AFPM D= avid G. Johnston <david.g.= johnston@gmail.com> wrote:
On Tue, Apr 16, 2024 at 1:27=E2=80=AF= PM Kirk Wolak <wol= akk@gmail.com> wrote:
= Could we make the PREPARE line read
...
No. That is a synt= ax excerpt and the prepare command doesn't accept an optional deallocat= e keyword at that position.

If we wanted to improve the psql help here we'd have two options:
Add to the descripti= on:
prepare a st= atement for execution (undo this with Deallocate)
=C2=A0
I=C2=A0 am 100% okay with that.=C2=A0 I woul= d consider DEALLOCATE to be caps so it looks like a command.

=
But would leave that to you guys...
Great observations= on the other issues.=C2=A0 Not looking to complicate things.=C2=A0 Just en= ough bread crumbs to link things.

Thanks!
--000000000000e7d11006164e8757--