[moved to hackers]
Is this a regression in the stable branches? If so, shouldn't we do a new
release rather immediately? What do others think about this situation?
Can you remember regressions in stable branches in the past? How were those
it handled? I think "waiting for months" (i.e. for the next major bug fixes)
is not the correct answer here. IMHO, the latest released version should be
known best in all components.
Best Regards,
Michael Paesold
Bruce Momjian wrote:
Michael Fuhr wrote:
On Thu, Oct 13, 2005 at 09:49:20AM -0600, Michael Fuhr wrote:
> ecpg in 8.0.4 seems not to like the macros. I get the same error,
> but not if I do this:
>
> VARCHAR t[256];
> VARCHAR o[256];
>
> ecpg in 8.1beta3 works either way.
This appears to be the guilty commit, which was made to 7.4, 8.0,
and HEAD (8.1):
http://archives.postgresql.org/pgsql-committers/2005-08/msg00266.php
It was recently fixed in HEAD only:
http://archives.postgresql.org/pgsql-committers/2005-10/msg00043.php
Good catch! I have backpatched these fixes to the 8.0 and 7.4 branches
as you suggested, (identical) patches attached.
The big problem is that we might not make releases on these branches for
months, so anyone needing the fix should download CVS for those
branches.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
