Re: Any real known bugs about wrong selects?

Hello David,
I was relay on postgresql for years and now got trouble like you are
talking about, but i did not solve it yet to be sure that this in not
a matter of my hands but a problem of PG.
See [GENERAL] insertion with trigger failed unexpectedly
Discussion. Many people trying to help me so if it is not a PG problem i
could tell you that i'm using PG for 4 years at least in a some
number of sites (low traffic huge bases, very high traffic sites,
combined) and have had no problems.

Regards,
Anton Nikiforov
DT> Hi,

DT> we are currently using another database product but besides some
DT> licensing issues we are finding more and more problems with the
DT> database. We are evaluating PostgreSQL and it looks quite handy.
DT> Interesting features paired with good performance and a lot of users
DT> seems to be a prove for the quality.

DT> I wonder if people encountered bugs like 'a select returns a wrong
DT> number of rows' or any other very serious bugs. We do not have problems
DT> with things like database crashes (because we already needed to check
DT> and fix such things with the other database product) or with slow
DT> execution time in some cases but we take it very serious if a bug
DT> results in -wrong- result sets because we are calculating bills and
DT> other things which is very sensible to wrong results from select
DT> statements.

DT> As PostgeSQL is not a commercial product i hope that we are getting
DT> real, more reliable answers about bugs than from the database producer
DT> whose product we are using since now.

DT> Regards David


DT> ---------------------------(end of broadcast)---------------------------
DT> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org