#12 Postgresql insertion failure

[Tony Harper]

My database corrupted so I created a new one. I had
made a partial back up on another database platform
(albums, tracks, artists). I inserted the backed up
records into the new Postgresql database. My music
directory that I'm pointed to is completely empty. With
ES now booted, I inserted a CD that is not in the new
postgresql database. The CD spins up, but does not rip
even though the CDROM is marked AutoRip. I look in
the Postgresql database and entries are there for the
Artist, Album, but no Track records. The interface
reports an Unknown CD (even though the freedb id for
this CD has been put in the Albums table). This
happened multiple times.
Today...I had time to revisit the issue. I created another
database. Copied the backed up records into the table
again. Did the same procedure as noted above and got
the same result. On this attempt and the previous one,
I did notice that Postgresql was using IDs (for artist and
album) that had not been used before but lower in #
than the last backed up id number.....an example would
probably be best

Backed up record sample:

Artist ID Artist
2 Prince
9 John Mellencamp
15 Natilie Merchant

Now after I copied these records into my new empty
database AND then stuck in a Rolling Stones CD, the
newly inserted artist ID might be
7 Rolling Stones

So, I began to think that perhaps it was an ID issue
somehow....so I deleted all the records in the artists,
albums, tracks tables in the new Postgresql DB and
inserted a CD. It started ripping and inserted all the
correct information into the DB. Worked as it should.

So I guess my question is.....
Is ES doing something to determine an ID to insert into
the POSTGRESQL DB or are there some DB statistics
or something I need to update after I essentially bulk
updated the database.....