Horton

Re: Patch: plan invalidation vs stored procedures

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joshua Drake <jd@commandprompt.com>, Gregory Stark <stark@enterprisedb.com>, Hannu Krosing <hannu@2ndQuadrant.com>, Asko Oja <ascoja@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, Dimitri Fontaine <dfontaine@hi-media.com>, pgsql-hackers@postgresql.org, Andrew Dunstan <andrew@dunslane.net>, David Fetter <david@fetter.org>, Martin Pihlak <martin.pihlak@gmail.com>
Date: 2008-08-19T18:58:05Z
Lists: pgsql-hackers 
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Joshua Drake wrote:
> >> Is our backpatch policy documented? It does not appear to be in
> >> developer FAQ.
> 
> > Seems we need to add it.
> 
> I'm not sure that I *want* a formal written-down backpatch policy.
> Whether (and how far) to backpatch has always been a best-judgment call
> in the past, and we've gotten along fine with that.  I think having a
> formal policy is just likely to lead to even more complaints: either
> patching or not patching could result in second-guessing by someone
> who feels he can construe the policy to match the result he prefers.

OK, agreed.
-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +