Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b8ikq-0001X0-Vi for pgsql-docs@arkaria.postgresql.org; Fri, 03 Jun 2016 06:38:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b8ikq-00042W-H1 for pgsql-docs@arkaria.postgresql.org; Fri, 03 Jun 2016 06:38:48 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b8ikT-0003d6-U0 for pgsql-docs@postgresql.org; Fri, 03 Jun 2016 06:38:26 +0000 Received: from mail-io0-x231.google.com ([2607:f8b0:4001:c06::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1b8ikL-0000gm-Id for pgsql-docs@postgresql.org; Fri, 03 Jun 2016 06:38:24 +0000 Received: by mail-io0-x231.google.com with SMTP id o189so56263400ioe.2 for ; Thu, 02 Jun 2016 23:38:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=2R5eqzgnjKePoH1CsYR+FAcuGVIh52E/90qdPniA88A=; b=Zlh1qiM+GBHjvp8wxxLAylbdY8jVUvMqw5E8pXBAxN9A7TM6H8PWhWDB2mlOvE8D2N UhHelG7Bd3nwUnOtaVmSWzBynJ/gGs19qZabZPoTYEU+yNI9AdswGbwxm7XSZtWoTdVc zauFbJ92GOMgWE59ijAVTe4FsEr2+Q4TMX8YLvuiWFXG+CxCbEJzmuXVo/jU6ZfYdSNI Cr0cjBfm+4C9zuPJYnizz2ooSxdOZFPif/8NOLsixDTh7K8ICM8+zbcin7ywb+sVHmFM C4KxE7P1SXTwaNm9aioucIK8PwEk745Ylmc009qMyfIxXiv4oSx/8htX+zdRq/IGUtNF AKqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=2R5eqzgnjKePoH1CsYR+FAcuGVIh52E/90qdPniA88A=; b=F6YFrwcesAVSxS8EMeT8a0v6So1WuVSim8+rcOi6K9yejB+6R1a1mim4uL3VYtwCdd zeGUb78K2p6UgnYA5gYQozYaEZweIiJcVGkrKhTnuDjuU7LfcspFYDrC8X0nDtb7h/VC Se5ObWtBCnZVFxjQbCNl14eh6dFlLdMbmT2SrCc2kItcdvcr2mAUdaPTtLS5dbAaQm2J /0rMXietpfiGry7Y4lQL5Qif8l4J4wLXC1XIarfhxKZjSNcHdGMqmhiEws9fbdi0vJ6i uXU6NNcyJyl8x0pXO5dy7wdWjC8+cEtigvUvgiXSja7FUcDKXn0ieDHQwFI85iOnSOqT dWPw== X-Gm-Message-State: ALyK8tIunFeqzyoRGxlMA3nR1f+zlkkgWhJ/N6NY8zMwY8ZuQXLL0yAFDd9RHA/FLjUQBST4lvmP/K5IPSbK5A== MIME-Version: 1.0 X-Received: by 10.107.9.170 with SMTP id 42mr2649032ioj.53.1464935896436; Thu, 02 Jun 2016 23:38:16 -0700 (PDT) Received: by 10.79.130.131 with HTTP; Thu, 2 Jun 2016 23:38:16 -0700 (PDT) In-Reply-To: <956686ed-b753-14af-dc58-53627a860d69@2ndquadrant.com> References: <956686ed-b753-14af-dc58-53627a860d69@2ndquadrant.com> Date: Fri, 3 Jun 2016 09:38:16 +0300 Message-ID: Subject: Re: pg_prepared_statements From: Dmitry Igrishin To: Peter Eisentraut Cc: pgsql-docs Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 2016-06-03 7:37 GMT+03:00 Peter Eisentraut : > On 6/2/16 1:59 AM, Dmitry Igrishin wrote: >> >> I suggest to use phrase "the PREPARE SQL command" at >> >> https://www.postgresql.org/docs/current/static/view-pg-prepared-statements.html >> Thus, I would replace: >> >> "For prepared statements created via SQL, this is the PREPARE >> statement submitted by the client. For prepared statements created via >> the frontend/backend protocol, this is the text of the prepared >> statement itself." >> to >> "For prepared statements created via SQL, this is the PREPARE SQL >> command submitted by the client. For prepared statements created via >> the frontend/backend protocol, this is the statement itself." >> >> "true if the prepared statement was created via the PREPARE SQL statement" >> to >> "true if the prepared statement was created via the PREPARE SQL command" > > > I'm not sure why that is better. "statement" is the standard term in these > contexts. According to https://www.postgresql.org/docs/current/static/sql-prepare.html "statement" is a text of statement without "PREPARE". So, the phrase "PREPARE statement" not absolutely clear. And according to https://www.postgresql.org/docs/current/static/sql-commands.html the PREPARE is a SQL command, rather than SQL statement. -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs