The following bug has been logged online: Bug reference: 1242 Logged by:
Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.3 Operating system: Linux Debian 3.1 Description: Major bug in pgSQL Details: Hi, apparently we have found a critical bug in pgSQL. At the present moment we can not reproduce it, but here is the description: Foreword: we have a very high loaded pgSQL-based application with thousands of simultaneous users and overall 20 high performance server. Another nice-to-know thing to mention - we have very large transaction blocks, with some hunderds of SQL statements in each block. Problem: in some cases we experience the following problem - we have found in the database some _absolutely_ identical rows, despite the fact, that we have defined some unique (!) indexes on some of the fields and even primary (!) keys, we can see, that the rows are _exactly_ the same. In some cases we have seen up to 7 absolutely identical rows, with the same primary keys and the same unique indexed fields. This problem is in our eyes absolutely critical. We are even considering right now the change to another DBMS :(, even though we were in the past always very satisfied with pgSQL... We are looking forward to hear, if there are any known solutions for this kind of problem. Thank you very much! ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
