From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Peter Schmidt" <peterjs(at)home(dot)com> |
Cc: | "Sean Chittenden" <sean(at)chittenden(dot)org>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: FreeBSD upgrade causes performance degredation |
Date: | 2001-11-01 03:55:06 |
Message-ID: | 15012.1004586906@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Peter Schmidt" <peterjs(at)home(dot)com> writes:
> Old function was something like this:
> SELECT COL1 FROM TABLE WHERE COL2 = SP_FUNCTION(ARG, ARG, ARG, ...)
> The query was modified so that the call to the second function was executed
> as a subselect (and thereby executed only once for all rows in the first
> select?):
> SELECT COL1 FROM TABLE WHERE COL2 = (SELECT SP_FUNCTION(ARG, ARG,
> ARG...))
This seems like a rather klugy substitute for marking the function
"iscachable". You might want to read up on that in the CREATE FUNCTION
documentation.
I don't see why an OS change would affect this though; I think you still
have more digging to do to understand the issue. Did you reinstall
Postgres after the OS update, and if so is it possible you neglected to
do VACUUM ANALYZE after reloading the database?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-11-01 04:28:05 | Re: backup file system |
Previous Message | Jeremy Buchmann | 2001-11-01 00:26:53 | Re: backup file system |