| From: | Austin Swinney <austin(at)interactivate(dot)com> |
|---|---|
| To: | pg novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | catching up an id sequence |
| Date: | 2004-07-29 21:21:59 |
| Message-ID: | 53BA885A-E1A5-11D8-B954-000A95B2A15E@interactivate.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Hi most esteemed novices and experts. It is an honor to post here!
I imported a MySQL dump into PostgreSQL (7.4.3) and was wondering what
a good way to catch up the ID sequence table to be current with the
table I imported.
In the Perl app associated with the DB, I swapped out currval for
mysql_insertid. Then I noticed that the currval reported is started
from 0, but there are already 1400+ records in that table that have id
numbers.
The definition in question is:
messageid | integer | not null default
nextval('public.message_messageid_seq'::text)
Ideas? Many thanks!
Austin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-07-29 22:01:07 | Re: catching up an id sequence |
| Previous Message | Betsy Barker | 2004-07-29 18:32:31 | Re: Calling a function that returns a composite type using |