Re: Support prepared statement invalidation when result types change - Mailing list pgsql-hackers

From Andy Fan
Subject Re: Support prepared statement invalidation when result types change
Date
Msg-id CAKU4AWpd82LBE=T-=Dyf_6cHSP+sbo9-tKH5tdxEu5V0BX0yUA@mail.gmail.com
Whole thread Raw
In response to Support prepared statement invalidation when result types change  (Jelte Fennema <me@jeltef.nl>)
Responses Re: Support prepared statement invalidation when result types change
List pgsql-hackers
Hi, 
 

This requirement was not documented anywhere and it
can thus be a surprising error to hit. But it's actually not needed for
this to be an error, as long as we send the correct RowDescription there
does not have to be a problem for clients when the result types or
column counts change.

What if a client has *cached* an old version of RowDescription
and the server changed it to something new and sent resultdata
with the new RowDescription.  Will the client still be able to work
expectly? 

I don't hope my concern is right since I didn't go through any of
the drivers in detail, but I hope my concern is expressed correctly. 


--
Best Regards
Andy Fan

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] Add inline comments to the pg_hba_file_rules view
Next
From: Andres Freund
Date:
Subject: Re: Have better wording for snapshot file reading failure