Re: Segmentation fault.

> "Andrei N.Sobchuck" <andrei(at)mart(dot)cherkassy(dot)ua> writes:
> > But one query fails when I use search on boolean field.
>
> What's the query exactly? I don't see any evidence in your backtrace
> that the function is being invoked, so I doubt that has anything to do
> with the problem.

I'm using PostgreSQL on linux 2.2.13, glibc 2.1.3, compiled by gcc 2.95.3
with --enable-multibyte=KOI8.

Below You can see an example of query that crashes backend. The query was
generated by MSAccess. It works fine without "tel" = 1 (tel is boolean). Or
with "tel"=1, but without EXISTS-subquery.
=======
SELECT "object"."id_object" FROM "object" WHERE (((((((("status" = 1 ) AND
("tel" = 1 ) ) ) ) ) AND NOT(EXISTS (SELECT "po"."id_person" FROM
"person_object" "po" WHERE (("po"."id_person" = 17 ) AND ("po"."id_object" =
"object"."id_object" ) ) )) ))) ORDER BY "object"."komnat"
,"object"."tekushaja_cena"
=======
I have a try for reproducing the bug. I have done "SELECT * INTO o FROM
object" and then I've executed the query with "o" (not "object") as source
table. Backend was not terminated. And more. The query on "object" table
works without any problems (in that session).
At now, I quit from "psql" and then run it again. Oops. Executing the query
on table named "object" terminate the backend. (But, after executing the
query on "o"-table, the query on "object" works fine. In current session.).

P.S.Is another way to work with boolean type field from MS Access?

> regards, tom lane
>
>