Yes, but the table in question have 3 PK and only one that needs this "sequence" so I just thought instead of getting holes in the IDs I just manually handle this counter somehow.. Not a big deal but... :)
You'd only get holes if you keep making nextval requests without using the value - say by issuing rollback. The problem with holes is actually the feature of uniqueness SEQUENCES provides. Perhaps you judge that there is too high a chance of rollback to create a sufficient number of holes to warrant not using a SEQUENCE.
It's all down to your application and specific situation I guess however your counter table idea sounds exactly like what SEQUENCE provides, without any of the guarantees.
I think I'd still recommend using a SEQUENCE for anything but the most profound reason :)
--
Rob Fielding [EMAIL PROTECTED] Development Designer Servers Ltd
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
