Skip site navigation (1) Skip section navigation (2)

Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe

From: David Wheeler <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Neil Conway <neilc(at)samurai(dot)com>, pgsql-general(at)postgresql(dot)org,dbdpg-general(at)gborg(dot)postgresql(dot)org
Subject: Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Date: 2005-05-02 16:53:12
Message-ID: 2AD2301D-17EF-4E50-9B79-2801B1169FAA@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-general
On May 2, 2005, at 09:34 , Tom Lane wrote:

> I think you could demonstrate that if the spec is "make it look  
> like the
> original query was retyped as source each time", then *every* DDL  
> change
> in the database potentially requires invalidating every cached plan.
> I don't find that a desirable spec.

I agree. It seems to me that if someone is doing that sort of  
chicanery, then one should not use prepared statements. IOW, I would  
view it as an edge case.

Regards,

David

In response to

pgsql-general by date

Next:From: Hannes DorbathDate: 2005-05-02 17:21:54
Subject: Re: Persistent Connections in Webserver Environment
Previous:From: Tom LaneDate: 2005-05-02 16:47:18
Subject: Re: 7.3.9 Install Question - init.d/postgresql error?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group