title: PostgreSQL bigserial & nextval
body: <p>I've got a PgSQL 9.4.3 server setup and previously I was only using the public schema and for example I created a table like this:</p>
  
  <pre><code>CREATE TABLE ma_accessed_by_members_tracking (
      reference bigserial NOT NULL,
      ma_reference bigint NOT NULL,
      membership_reference bigint NOT NULL,
      date_accessed timestamp without time zone,
      points_awarded bigint NOT NULL
  );
  </code></pre>
  
  <p>Using the Windows Program PgAdmin III I can see it created the proper information and sequence.</p>
  
  <p>However I've recently added another schema called "test" to the same database and created the exact same table, just like before.</p>
  
  <p>However this time I see:</p>
  
  <pre><code>CREATE TABLE test.ma_accessed_by_members_tracking
  (
    reference bigint NOT NULL DEFAULT nextval('ma_accessed_by_members_tracking_reference_seq'::regclass),
    ma_reference bigint NOT NULL,
    membership_reference bigint NOT NULL,
    date_accessed timestamp without time zone,
    points_awarded bigint NOT NULL
  );
  </code></pre>
  
  <p>My question / curiosity is why in a <code>public</code> schema the <code>reference</code> shows <code>bigserial</code> but in the <code>test</code> schema <code>reference</code> shows <code>bigint</code> with a <code>nextval</code>?</p>
  
  <p>Both work as expected. I just do not understand why the difference in schema's would show different table creations. I realize that bigint and bigserial allow the same volume of ints to be used.</p>