From: | Bob Pawley <rjpawley(at)shaw(dot)ca> |
---|---|
To: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PG Admin |
Date: | 2006-12-04 23:40:48 |
Message-ID: | 00f601c717fd$a0217360$8e904618@owner |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
When a row is deleted the serial number and oid are also deleted. The
sequence then has gaps which are inadmissible.
Bob
----- Original Message -----
From: "Tony Caduto" <tony_caduto(at)amsoftwaredesign(dot)com>
To: "Bob Pawley" <rjpawley(at)shaw(dot)ca>; <pgsql-general(at)postgresql(dot)org>
Sent: Monday, December 04, 2006 10:43 AM
Subject: Re: [GENERAL] PG Admin
> Bob Pawley wrote:
>> That's what they are doing.
>>
>> That is also what I am looking for, if it is accessable. If so, I can use
>> that information to add a sequential numerical element to my information
>> that doesn't have the restrictions of a serial column.
>>
>> Bob
>>
> Hi Bob,
>
> Well, if you create your tables WITH OIDs then each row has a OID
> associated with it.
>
> What exactly are the restrictions of a serial column? It's just standard
> integer value with a default value that calls the nextval function.
>
> Later,
>
> --
> Tony Caduto
> AM Software Design
> http://www.amsoftwaredesign.com
> Home of PG Lightning Admin for Postgresql
> Your best bet for Postgresql Administration
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2006-12-04 23:53:39 | Re: PG Admin |
Previous Message | Michael Glaesemann | 2006-12-04 23:14:36 | Re: pgsql bug found? |