From: | "Jim Wilson" <jimw(at)kelcomaine(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: planner and join type mismatches |
Date: | 2004-01-14 15:46:18 |
Message-ID: | twig.1074095178.64519@kelcomaine.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> said:
> "Jim Wilson" <jimw(at)kelcomaine(dot)com> writes:
> > Re: tip 9 :-). In 7.3.5 is it possible that the planner is finding a type
> > mismatch when there isn't one, resulting in a seq scan being selected?
>
> When you gave no details, how is anyone to know? For questions like
> this, you need to post the table definitions, the exact query, and the
> results of EXPLAIN ANALYZE on that query. BTW, pgsql-performance is a
> more appropriate list than -general for such questions.
>
> regards, tom lane
My apologies. I think you did answer my question though, that there isn't a
well known problem as described (in it's general scope). As soon as I get a
chance I will put together a test case and post the issue to psql-performance.
Best,
Jim Wilson
From | Date | Subject | |
---|---|---|---|
Next Message | Keith C. Perry | 2004-01-14 15:56:01 | Re: Best practice? Web application: single PostgreSQL |
Previous Message | Mike Nolan | 2004-01-14 15:45:30 | Schemas not created on restore |