Hi All,
I'm running a site that has a reasonable amount of traffic 24/7 , writes and reads.
I've found that when I add a new column, I sometimes get a spike of errors on the application side due to prepared
statementquery plans getting invalidated, causing transactions to rollback.
The error is:
ERROR: cached plan must not change result type
Is there a way to make postgres recalculate the query plan instead of failing the transaction when a new column is
added?
Thanks,
Daniel Heath