public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Jeff Davis <[email protected]>
Cc: [email protected]
Subject: Re: FE/BE docs and unsigned integers
Date: Thu, 02 Jan 2014 13:41:11 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <1388686291.19125.437.camel@jdavis>
References: <1388686291.19125.437.camel@jdavis>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

Jeff Davis <[email protected]> writes:
> 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?

I think it was just laziness, and/or not wanting to add a uint32 type
to the documentation's notation, since (IIRC) there aren't any places
where a field is unsigned and that really matters to the protocol.

If you think it's worth being more precise, feel free to submit a patch.

			regards, tom lane


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

view thread (2+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: FE/BE docs and unsigned integers
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox