Home Explore Blog CI



postgresql

67th chunk of `doc/src/sgml/protocol.sgml`
add374c10a8905380dafb0cc6edbef2dee05630a55add0160000000100000fa0
 including self.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>String</term>
       <listitem>
        <para>
         The name of the run-time parameter being reported.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>String</term>
       <listitem>
        <para>
         The current value of the parameter.
        </para>
       </listitem>
      </varlistentry>
     </variablelist>
    </listitem>
   </varlistentry>

   <varlistentry id="protocol-message-formats-Parse">
    <term>Parse (F)</term>
    <listitem>
     <variablelist>
      <varlistentry>
       <term>Byte1('P')</term>
       <listitem>
        <para>
         Identifies the message as a Parse command.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>Int32</term>
       <listitem>
        <para>
         Length of message contents in bytes, including self.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>String</term>
       <listitem>
        <para>
         The name of the destination prepared statement
         (an empty string selects the unnamed prepared statement).
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>String</term>
       <listitem>
        <para>
         The query string to be parsed.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>Int16</term>
       <listitem>
        <para>
         The number of parameter data types specified
         (can be zero).  Note that this is not an indication of
         the number of parameters that might appear in the
         query string, only the number that the frontend wants to
         prespecify types for.
        </para>
       </listitem>
      </varlistentry>
     </variablelist>

     <para>
      Then, for each parameter, there is the following:
     </para>

     <variablelist>
      <varlistentry>
       <term>Int32</term>
       <listitem>
        <para>
         Specifies the object ID of the parameter data type.
         Placing a zero here is equivalent to leaving the type
         unspecified.
        </para>
       </listitem>
      </varlistentry>
     </variablelist>
    </listitem>
   </varlistentry>

   <varlistentry id="protocol-message-formats-ParseComplete">
    <term>ParseComplete (B)</term>
    <listitem>
     <variablelist>
      <varlistentry>
       <term>Byte1('1')</term>
       <listitem>
        <para>
         Identifies the message as a Parse-complete indicator.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>Int32(4)</term>
       <listitem>
        <para>
         Length of message contents in bytes, including self.
        </para>
       </listitem>
      </varlistentry>
     </variablelist>
    </listitem>
   </varlistentry>

   <varlistentry id="protocol-message-formats-PasswordMessage">
    <term>PasswordMessage (F)</term>
    <listitem>
     <variablelist>
      <varlistentry>
       <term>Byte1('p')</term>
       <listitem>
        <para>
         Identifies the message as a password response. Note that
         this is also used for GSSAPI, SSPI and SASL response messages.
         The exact message type can be deduced from the context.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>Int32</term>
       <listitem>
        <para>
         Length of message contents in bytes, including self.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term>String</term>
       <listitem>
        <para>
         The password (encrypted, if requested).
        </para>
       </listitem>
      </varlistentry>
     </variablelist>
    </listitem>
   </varlistentry>

   <varlistentry id="protocol-message-formats-PortalSuspended">
    <term>PortalSuspended (B)</term>
    <listitem>
     <variablelist>

Title: PostgreSQL Protocol Message Formats
Summary
This section continues to describe the formats of various PostgreSQL protocol messages, including Parse, ParseComplete, PasswordMessage, and PortalSuspended, detailing the structure and content of each message type, such as message identifiers, lengths, query strings, parameter data types, and passwords, which are used to handle parsing, authentication, and portal suspension in PostgreSQL database operations.