In response to Geoffrey <esoteric@xxxxxxxxxxxx>: > We are trying to track down an issue with our PostgreSQL application. > We are running PostgreSQL 7.4.13 on Red Hat Enterprise ES 3. > > We have a situation where the postgres backend process drops core and > dies. We've tracked this to an unusual situation where a sequence value > that is being created during the process that is causing the core file > generation. The thing that is bizarre is that the sequence value skips > 30+ entries. > > How is this even possible? Any suggestions would be greatly appreciated. Don't know why your workers are dropping cores: backtraces and the like would probably help sort that out. However, when a transaction requests a new sequence, then aborts (for whatever reason) that sequence isn't going to back up. My understanding is that the overhead to making sequences transaction aware and able to avoid gaps is more than anyone has determined the benefit to be. What is the problem with gaps? If you're afraid of running out of numbers, switch to BIGSERIAL. -- Bill Moran Collaborative Fusion Inc.
