From: Kirk Wolak <wolakk@gmail.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Update Help on PREPARE to mention DEALLOCATE
Date: Wed, 17 Apr 2024 13:52:57 -0400
Message-ID: <CACLU5mQsPS4-+JZN5DTY_JB7mRZB1CdFbk7VcJV6yDRKZUhXTg@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwa0CdWC2wsaGBdiBd22AvOShy=qnDU-fpkNj_3cfc8RzQ@mail.gmail.com>
References: <CACLU5mRsdYaEr+y=rYr6_rHJRoW49vTnSLdrcwwN2K0fONupJg@mail.gmail.com>
<CAKFQuwa0CdWC2wsaGBdiBd22AvOShy=qnDU-fpkNj_3cfc8RzQ@mail.gmail.com>
On Tue, Apr 16, 2024 at 4:42 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:
> On Tue, Apr 16, 2024 at 1:27 PM Kirk Wolak <wolakk@gmail.com> wrote:
>
>> 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!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: wolakk@gmail.com, david.g.johnston@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Update Help on PREPARE to mention DEALLOCATE
In-Reply-To: <CACLU5mQsPS4-+JZN5DTY_JB7mRZB1CdFbk7VcJV6yDRKZUhXTg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox