Dave Page wrote:
> On Tue, Dec 22, 2009 at 8:43 PM, Ashish Anand
> wrote:
> > Alvaro, Please read the?first?three mails in this thread.
> >
> > Dave, can you open a bug at your end. Just open it so that it can be tracked
> > two months down the line. I am not insisting on fixing it right now.
>
On Thu, Feb 18, 2010 at 11:09, Tim Bunce wrote:
> The key line is:
>
> *PLPerl::utf8::SWASHNEW = \&utf8::SWASHNEW;
Hrm... It seems to work for me in HEAD and AFAICS we dont have that
line. Did I just miss it? Or did you happen to fix it in another way
with your refactoring?
Another Idea tha
On Thu, Feb 18, 2010 at 02:20, wrote:
> $ psql -U foo -h 127.0.0.1 -f doesntwork.sql db
> Password for user foo:
> ERROR: invalid byte sequence for encoding "UTF8": 0xe46976
> HINT: This error can also happen if the byte sequence does not match the
> encoding expected by the server, which is co
On Thu, Feb 18, 2010 at 10:50:23AM +, Tim Bunce wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5334
> Logged by: Tim Bunce
> Email address: tim.bu...@pobox.com
> PostgreSQL version: 8.4.2
> Operating system: OS X
> Description:Version 2.22
The following bug has been logged online:
Bug reference: 5333
Logged by:
Email address: pekka.jarvi...@gmail.com
PostgreSQL version: 8.4
Operating system: Ubuntu Karmic Koala
Description:psql returns 0 on error
Details:
$ psql -U foo -h 127.0.0.1 -f doesntwork.sql
The following bug has been logged online:
Bug reference: 5335
Logged by: Tim Bunce
Email address: tim.bu...@pobox.com
PostgreSQL version: 8.4.2
Operating system: OS X
Description:GUC value lost on exception
Details:
andrew=# SET SESSION plperl.use_strict = on;
SE
The following bug has been logged online:
Bug reference: 5334
Logged by: Tim Bunce
Email address: tim.bu...@pobox.com
PostgreSQL version: 8.4.2
Operating system: OS X
Description:Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL
8.4
Details:
Version 2.22 of th
