Merlin Moncure wrote:
> My previous employer contacted me today. Apparently they are having
> an increasing frequency of occurances where they disocover violations
> of the primary key constraint not being caught by the database. This
> system is an ISAM emulation system, and it relies heavily on the
> database throwing unique constraint violations to approximately
> provide a cobol rewrite statement.
>
> These errors are never caught when they occur. One way they are
> caught is during a dump/reload, the record fails to reinsert.
>
> I brought this up around a year ago, and the issue was never
> successfully resolved. These are windows systems running PostgreSQL
> 8.0.x.
>
> any thoughts?
Do they vacuum enough? I have seen problems with PostgreSQL (albeit not
since 7.3) where a unique constraint would not enforce because of index
bloat.
Sincerely,
Joshua D. Drake
>
> merlin
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
