Re: BUG #5290: Simple loop with insert into and check to avoid duplicate values fails

From: Wild Wezyr <wildwezyr(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, WildWezyr <wi(dot)ld(dot)we(dot)zy(dot)r(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5290: Simple loop with insert into and check to avoid duplicate values fails
Date: 2010-01-21 08:59:09
Message-ID: 94a2fe2c1001210059y26fdfdb3gc38c37b36a3b433b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2010/1/20 Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>

>
> I happen to have access to a Win32 virtual machine just now. CVS HEAD,
> built from sources on the VM.
>
> Seems to work fine. The test case runs for ages, I'm at about 1/3
> through it, and no errors this far. I'm going to have to kill it now.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>

What OS you have on this Win32 box? Is it Windows Vista (like mine)?

What version of Postgres you have used? Is it 8.3.3 or 8.4.2 like mine?

What encoding/collation was your DB created with? Was it UTF8 /
'Polish_Poland.1250' ? As I posted - standard 'C' collation gives no errors,
so it is important to use 'Polish_Poland.1250' (this is one of three choices
I have on my box: 'C' / 'Polish_Poland.1250' / 'Posix').

If my code runs for long with no error - it is best to interrupt and than
run it again - it gives errors in unpredictable manner (but only for
'Polish_Poland.1250' collation)...

(WW)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2010-01-21 09:10:13 Re: BUG #5290: Simple loop with insert into and check to avoid duplicate values fails
Previous Message Antoine Banks 2010-01-21 08:53:00 PHP .zip File