Re: [HACKERS] Query returning tuples that does not satisfy the WHERE clause
Manuel Sugawara writes: > I don't think so, search_path has its default value and also I'm able > to reproduce it in a fresh cluster (tried 3 different machines to > discard hardware problems). Hm, well I'm willing to take a look if you can provide me access to the problem database running on a debug-enabled Postgres build. The fresh-cluster test seems to rule out my other idea about a corrupt index (though that was shaky anyway considering both plans use the same index...) regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Query returning tuples that does not satisfy the WHERE clause
Tom Lane <[EMAIL PROTECTED]> writes: > You seem to have worse problems than that, because as given the > insc_registra_grupo function never returns non-NULL Actually the function (and the database) is quite complex and was trimed just to test the problem. > I suspect pilot error --- perhaps looking at the wrong schema or > some such? I don't think so, search_path has its default value and also I'm able to reproduce it in a fresh cluster (tried 3 different machines to discard hardware problems). Regards, Manuel. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Query returning tuples that does not satisfy the WHERE clause
Manuel Sugawara writes: > Using the second plan the query is returning tuples where >a=F1o_semestre <> 20071 You seem to have worse problems than that, because as given the insc_registra_grupo function never returns non-NULL, and so the query ought not be returning any tuples at all. I suspect pilot error --- perhaps looking at the wrong schema or some such? regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
