Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> 1) People preparing statements to save on parse+plan time; and
> 2) People preparing statements to get convenenient param placement.
> I suspect that most of (1) also want (2), but many of (2) don't care much
> about (1) and are just preparing statements for sql-injection safety (param
> placement), because they've been told to by someone, because their library
> does it for them, etc.
> So: Would it be easier to handle control of replan vs no-replan at PREPARE
> time? Or would that have very much the same protocol/pl change issues?
Submits a command to the server and waits for the result, with the
ability to pass parameters separately from the SQL command text.
So I think what you're talking about is already in there.
In response to
pgsql-hackers by date
|Next:||From: Devrim GÜNDÜZ||Date: 2010-02-28 09:48:48|
|Subject: Re: Anyone know if Alvaro is OK?|
|Previous:||From: Mark Mielke||Date: 2010-02-28 07:52:55|
|Subject: Re: Avoiding bad prepared-statement plans.|