On Tue, 2 Aug 2005, Tom Lane wrote:

> "Marc G. Fournier" <scrappy@postgresql.org> writes:
>> On Tue, 2 Aug 2005, Tom Lane wrote:
>>> Given the name, this could be a SERIAL column's sequence --- which is
>>> not dumped as a separate object by pg_dump, since recreating the SERIAL
>>> column ought to create it.
>
>> One of their functions does an insert into the table with
>> "nextval('xa_url_id_seq'::text)" as part of the INSERT itself, so they
>> aren't using that field as a SERIAL type ... just checked the CREATE TABLE
>> for teh table, and its defined as a "bigint NOT NULL" ...
>
> Hmm, odd. But maybe there are traces of a SERIAL linkage? What do
> you get from
>
> select * from pg_depend where objid = 'xa_url_id_seq'::regclass;

# select * from pg_depend where objid = 'xa_url_id_seq'::regclass;
classid | objid | objsubid | refclassid | refobjid | refobjsubid | deptype
---------+--------+----------+------------+----------+-------------+---------
1259 | 335539 | 0 | 16672 | 2200 | 0 | n
1259 | 335539 | 0 | 1259 | 335541 | 1 | i
(2 rows)

'k, checking the docs ... deptype == i is an INTERNAL, and refobjid is
what is referencing it (in this case, xa_url, as I'd expect) ... but,
looking at \d for xa_url, I'm not seeing anything there to cause it ... no
serial values ... the only 'default nextval()' I can find in the schema
is something totally unrelated ...

next?

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly