Re: Update Help on PREPARE to mention DEALLOCATE

2024-04-16 Thread David G. Johnston
On Tue, Apr 16, 2024 at 1:27 PM Kirk Wolak wrote: > Could we make the PREPARE line read > > PREPARE [ DEALLOCATE ] ...? > > So it's more consistent, and the user using a PREPARE gets a clue to > DEALLOCATE? > > No. That is a syntax excerpt and the prepare command doesn't accept an optional deallo

Update Help on PREPARE to mention DEALLOCATE

2024-04-16 Thread Kirk Wolak
Please notice this exchange: 16:20:02 devuser@nctest= # \h deallocate Command: DEALLOCATE Description: deallocate a prepared statement Syntax: DEALLOCATE [ PREPARE ] { name | ALL } URL: https://www.postgresql.org/docs/16/sql-deallocate.html 16:20:11 devuser@nctest= # \h PREPARE Command:

pg_createsubscriber: A more precise link to the initial data sync

2024-04-16 Thread Pavel Luzanov
Please consider a small correction of the link to the initial data synchronization section on the pg_createsubscriber page. -- Pavel Luzanov Postgres Professional:https://postgrespro.com From d040324464d5ef4cefd63e4d34373a90e2496b57 Mon Sep 17 00:00:00 2001 From: Pavel Luzanov Date: Tue, 16 Apr

Re: three small improvements for "Composite Types" page

2024-04-16 Thread Anton Voloshin
On 12/04/2024 23:44, David G. Johnston wrote: I'd much prefer to leave "different kind" alone and turn the immediately following, first-on-the-page, instance of CREATE TYPE into a link. Good, I'm fine with that too.  2. make first mention of CREATE TABLE a link [...] > I'm not all that convi