From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Add Unicode support in PL/Python |
Date: | 2009-09-13 22:12:47 |
Message-ID: | 1252879967.26439.22.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On sön, 2009-09-13 at 10:07 -0400, Andrew Dunstan wrote:
> >>> Add Unicode support in PL/Python
> >> The buildfarm seems quite unhappy with this patch.
> > I am completely unable to reproduce the buildfarm failures, even with
> > different Python versions and the exact configure options that the
> > buildfarm instances use. Does anyone have an affected build and wants
> > to work through this with me?
> I am going out shortly, but if you send me your ssh PK before I go I
> will set you an account up on dungbeetle which is failing and you can
> play there.
This is fixed now.
The reason this was not reproducible manually but showed up so
dramatically in the build farm is that almost all buildfarm machines use
SQL_ASCII as server encoding. While it's evidently good that we have
some machines testing that, we should probably also have more machines
testing the UTF8 and other code paths. Also, perhaps I'm missing
something, but it could have helped if the buildfarm logs showed the
locale and/or encoding somewhere.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-13 22:18:22 | pgsql: Write psql's ~/.psql_history file using history_truncate_file() |
Previous Message | Peter Eisentraut | 2009-09-13 22:07:06 | pgsql: Fix Unicode support in PL/Python Check calls of |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-09-13 22:23:04 | Re: [COMMITTERS] pgsql: Add Unicode support in PL/Python |
Previous Message | Marcos Luis Ortiz Valmaseda | 2009-09-13 21:51:02 | Re: New features on 8.5 !!!! |