On Sun, 2003-10-19 at 17:09, Tom Lane wrote:
> Michael Meskes <[EMAIL PROTECTED]> writes:
> > Does anyone know this bug report:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204000
> 
> The bug reporter is in error to be claiming he is running 7.3.3, because
> the assert() in question is at line 334 not 331 in 7.3.3.  He may have
> 7.3.3 client libraries, but he must be talking to a server version
> between 7.3 and 7.3.2.

This is curious because the version numbers are automatically generated
by reportbug and he gives no hint that he is talking to a different
machine.

However I verified that the assertion is at line 334 in the source code
that the package was compiled from.

> I believe the bug probably is the same one reported/fixed here:
> 
> 2003-04-20 13:37  tgl
> 
>       * src/backend/regex/regcomp.c (REL7_3_STABLE): Fix char-vs-pg_wchar
>       confusion in p_ere(), per failure report from Tom O'Dowd.  This fix
>       is not relevant to CVS tip anymore, but we should fix it in 7.3.*.
> 
> which would mean that it is indeed fixed in 7.3.3.  I suppose the reason
> Oliver never forwarded this report is he couldn't duplicate it...

It's more because I was away at the time fetching my mother-in-law from
Israel, so this bug never got dealt with at all :-(  But I do have
problems with these character set bugs, since it took a long time to
find a way to see these characters correctly.

I can confirm it does not happen in 7.4beta4

-- 
Oliver Elphick                                [EMAIL PROTECTED]
Isle of Wight, UK                             http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
                 ========================================
     "Commit thy way unto the LORD; trust also in him and 
      he shall bring it to pass."          Psalms 37:5 


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to