Re: First decent PostgreSQL CBT now on techdocs.postgresql.org - Mailing list pgsql-general

From Bruce Momjian
Subject Re: First decent PostgreSQL CBT now on techdocs.postgresql.org
Date
Msg-id 200112281752.fBSHqqT24715@candle.pha.pa.us
Whole thread Raw
In response to Re: First decent PostgreSQL CBT now on techdocs.postgresql.org  (Joe Conway <joseph.conway@home.com>)
Responses Re: First decent PostgreSQL CBT now on techdocs.postgresql.org
List pgsql-general
> > What I'm hoping to get is constructive feedback, as I've put as much
> > time, thought, and effort into this first one as I know how to.  I'm
> > talking HEAPS.  Suggestions of what should be the subject of the next
> > CBT are also welcome.
>
> Two minor comments:
>
> First, in 7.2+ sequences are based on 8 byte integers on platforms which
> support them, so the default maxvalue is 9223372036854775807 instead of
> 2147483647.

I do have a question about that.  If I do this:

    test=> create table test (x serial);
    NOTICE:  CREATE TABLE will create implicit sequence 'test_x_seq' for SERIAL column 'test.x'
    NOTICE:  CREATE TABLE / UNIQUE will create implicit index 'test_x_key' for table 'test'
    CREATE
    test=> \d test
                               Table "test"
     Column |  Type   |                   Modifiers
    --------+---------+------------------------------------------------
     x      | integer | not null default nextval('"test_x_seq"'::text)
    Unique keys: test_x_key

    test=>

My column is an integer.  I assume that is 4 bytes on all platforms.  If
it isn't, how does it know if the receiving end supports 8 bytes
integers?

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: Troy.Campano@LibertyMutual.com
Date:
Subject: Re: Shutting down postgresql
Next
From: "Jeffrey W. Baker"
Date:
Subject: postgres processes spending most of their time in the kernel