Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vymk6-0001Sq-Qy for pgsql-docs@arkaria.postgresql.org; Thu, 02 Jan 2014 18:11:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vymk6-00046N-5o for pgsql-docs@arkaria.postgresql.org; Thu, 02 Jan 2014 18:11:38 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vymk5-00046E-71 for pgsql-docs@postgresql.org; Thu, 02 Jan 2014 18:11:37 +0000 Received: from mail-pd0-f176.google.com ([209.85.192.176]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vymk1-0002pg-N6 for pgsql-docs@postgresql.org; Thu, 02 Jan 2014 18:11:36 +0000 Received: by mail-pd0-f176.google.com with SMTP id w10so14375465pde.21 for ; Thu, 02 Jan 2014 10:11:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:to:date:content-type :mime-version:content-transfer-encoding; bh=BCJnoS6u8tcV0O9S/t4Uh6opv32nobfCgLShrHpOJLU=; b=Obcbaf6s1fh2hAMkQY7xKbjPGpw9AEu8yUnOD8A1Ez01iEPJzrQJ7+zk0Qv8UJOYNE RTw+K3aPFBTLmTX4akgKLVZvzy283s6KO5PZnVJGy7kiVNfhhDMNaOUip3JOpDOrVAem +5pkCI5YTOr+2A031qSX8Nelc8jUTuyo9w55M6d6pOeBtsiH6fK187tRB+MTnmenEi53 vn/IkqSZkg/oEZmadpCRjBf01U/PnxucJr3wmfCXa74bP0jSfymPm/SNszEZBtPFxVX/ 19TuqRGoIKF3MoIJV+uX0KYew242ak0wShICjvNcUqRe86pKSdHJwVRsw6Y5SRpnwFwO FZXw== X-Gm-Message-State: ALoCoQn4psAHEmKDWez8oCsPtUgiU6K6O/ZvTOSXh3sXgaEA9e4KyFKVB4q967FXI3PDc60H0sNW X-Received: by 10.68.138.226 with SMTP id qt2mr89427390pbb.65.1388686291962; Thu, 02 Jan 2014 10:11:31 -0800 (PST) Received: from [192.168.0.106] (c-69-181-249-16.hsd1.ca.comcast.net. [69.181.249.16]) by mx.google.com with ESMTPSA id un5sm43514653pab.3.2014.01.02.10.11.30 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 02 Jan 2014 10:11:31 -0800 (PST) Message-ID: <1388686291.19125.437.camel@jdavis> Subject: FE/BE docs and unsigned integers From: Jeff Davis To: pgsql-docs@postgresql.org Date: Thu, 02 Jan 2014 10:11:31 -0800 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) 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 The documentation doesn't give much of a hint that the protocol is using unsigned integers. For instance, under ParameterDescription here: http://www.postgresql.org/docs/9.3/static/protocol-message-formats.html it says that the object ID is an Int32, which is described here: http://www.postgresql.org/docs/9.3/static/protocol-message-types.html as just a plain 32-bit integer. But the code (e.g. getParamDescriptions()) is clearly reading it into an Oid, which is unsigned. Is there a reason this isn't clear? Is it meant to be ambiguous because (as far as the protocol is concerned) it's just an opaque 32 bits? It seems like it's worth a note somewhere at least. Regards, Jeff Davis -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs