| From: | CoL <col(at)mportal(dot)hu> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Mysterious performance of query because of plsql function in |
| Date: | 2004-07-02 14:23:44 |
| Message-ID: | cc3r5g$210k$1@news.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
hi,
Peter Alberer wrote:
> Hi there,
>
> i have a problem with a query that uses the result of a plsql function
> In
> the where clause:
>
> SELECT
> assignments.assignment_id,
> assignments.package_id AS package_id,
> assignments.title AS title,
> COUNT(*) AS Count
> FROM
> assignments INNER JOIN submissions ON
> (assignments.assignment_id=submissions.assignment_id)
> WHERE
> package_id=949589 AND
> submission_status(submissions.submission_id)='closed'
> GROUP BY
> assignments.assignment_id, assignments.package_id, assignments.title
> ORDER BY
> assignments.title;
>
> Postgres seems to execute the function "submission_status" for every row
> of
> the submissions table (~1500 rows).
what is submission_status actualy?
\df submission_status
Is the function submission_status called stable?
C.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edoardo Ceccarelli | 2004-07-02 18:50:26 | finding a max value |
| Previous Message | Bruno Wolff III | 2004-07-02 13:12:58 | Re: BUG #1186: Broken Index? |