Re: Prepared statements considered harmful

From: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
Cc: "Phil Frost" <indigo(at)bitglue(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Prepared statements considered harmful
Date: 2006-09-01 10:39:01
Message-ID: E1539E0ED7043848906A8FF995BDA579014DBEBE@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Anyway, your plan assumes that you have information to work
> with. The current system plans prepared queries with no
> information at all about parameters and people are advocating
> to keep it that way. I think a good first step would be the
> plan on first execution, like Oracle does.

Yup, it is also possible to try to find an obvious plan and only
delay planning (or part of the plan) when different inputs make a
big difference (like MaxDB and Informix).

Andreas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2006-09-01 10:40:53 Re: [pgsql-advocacy] Thought provoking piece on
Previous Message nhrcommu 2006-09-01 10:03:09 Training (from Thought provoking...)