I think you're looking to return set of record or something like that.
On Wed, May 21, 2008 at 4:37 AM, Frank Dekervel
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> Small update on this problem:
>
> Wouter Verhelst came to help debugging, and he determined that the 2 seconds
> were spent planning the qu
Hello,
Small update on this problem:
Wouter Verhelst came to help debugging, and he determined that the 2 seconds
were spent planning the query and not executing the query. (executing the
query is quick as seen in the query plan).
To avoid replanning this query all the time, Wouter suggest rep
Frank Dekervel <[EMAIL PROTECTED]> writes:
> this turns this query in an append of a whole lot of seq scan/ index scan's.
> These scans are predictably quick, but the "append" takes 5 seconds (and the
> numbers of the scans do not add up to the append actual time)
It says 5 milliseconds, not 5 s
Hello,
I have a strange performance problem with postgresql 8.3 (shipped with ubuntu
hardy) and a query that seems very simple:
explain analyze
SELECT * FROM (part LEFT OUTER JOIN part_lang ON part.id =
part_lang.id)
WHERE part.parent = 49110;
query plan here: http://front7
