[PgFoundry] Unsigned Data Types - Mailing list pgsql-hackers

From Ryan Bradetich
Subject [PgFoundry] Unsigned Data Types
Date
Msg-id e739902b0808142300j6f19ac9difa8fab753e568b9b@mail.gmail.com
Whole thread Raw
Responses Re: [PgFoundry] Unsigned Data Types  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
Hello all,

Here is the first pass at the unsigned data type I have been working on.

I am planning on adding these to the September 2008 commitfest wiki page.
The unsigned data type is not targeted for core, but for the uint PgFoundry project.

The uint.c.gz file is the main source file for the uint1, uint2, and uint4 data types.
The uing.sql.gz file contains the SQL statements to add the unsigned data type to the database.
The pg_atoui.c.gz file is based off the function in the PostgreSQL source code but works for unsigned data types instead of signed data types.
The Makefile is used to build the unsigned data type shared library on Linux.

The tests.tar.gz is my unit test suit that I worked on to make sure the unsigned integer types worked as expected.

The tests cover cases like:
    * table creation with the unsigned integer types.
    * comparision operations.
    * INSERT statements (binary and text forms).
    * COPY statements (binary and text forms).
    * unique btree index support.

In addition to correctness issues, I would also appreciate feedback on best practices and portability concerns.

For example:
   I doubt my Makefiles are very portable.
   What is the proper solution to handle this?  pgxs?

Thanks,

- Ryan

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal sql: labeled function params
Next
From: "Pavel Stehule"
Date:
Subject: Re: proposal sql: labeled function params