The following bug has been logged online:
Bug reference: 5532
Logged by: Michael Lewis
Email address: mikelikes...@gmail.com
PostgreSQL version: 9.0 trunk
Operating system: OS X
Description:Valid UTF8 sequence errors as invalid
Details:
I'm using Python to sanitize
The following bug has been logged online:
Bug reference: 5531
Logged by: Ola Sergatchov
Email address: ola_sergatc...@hotmail.com
PostgreSQL version: 8.1.18
Operating system: RedHat Linux 4.1.2-46
Description:REGEXP_ REPLACE causes connection drop
Details:
Passing l
Ola Sergatchov wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5531
> Logged by: Ola Sergatchov
> Email address: ola_sergatc...@hotmail.com
> PostgreSQL version: 8.1.18
> Operating system: RedHat Linux 4.1.2-46
> Description:REGEXP_ REPLACE cau
"Ola Sergatchov" writes:
> The following bug has been logged online:
> Bug reference: 5531
> Logged by: Ola Sergatchov
> Email address: ola_sergatc...@hotmail.com
> PostgreSQL version: 8.1.18
> Operating system: RedHat Linux 4.1.2-46
> Description:REGEXP_ REPLACE caus
"Michael Lewis" writes:
> I'm using Python to sanitize my logs from invalid UTF8 characters before
> COPYing them into postgres. I came across this one sequence that seems to
> be valid UTF8 (in the extended range I believe).
It is not valid. See http://tools.ietf.org/html/rfc3629 --- a sequenc
>
>
>
> It is not valid. See http://tools.ietf.org/html/rfc3629 --- a sequence
> beginning with ED must have a second byte in the range 80-9F to be
> legal, and this doesn't. The example you give would decode as U+DF2D,
> ie part of a surrogate pair, which is specifically disallowed in UTF8
> ---
Mike Lewis writes:
> I've run into a fair amount of unicode errors when trying to copy in log
> files. Would you recommend using bytea or another data type instead of text
> or varchar... or at least copying to a staging table with bytea's and
> filtering out invalid rows when moving it to the ma
Hi all,
I downloaded the "one-click" installer for PostgreSQL 9.0 beta2 for Windows x64
(postgresql-9.0.0-beta2-windows-x64.exe) and installed it on my Windows 7 64
bit system. Installation seemed to go off without a hitch, but when I tried to
link to libpq in my project I received the followin
On 06/30/10 3:23 PM, Bidski wrote:
Hi all,
I downloaded the "one-click" installer for PostgreSQL 9.0 beta2 for
Windows x64 (postgresql-9.0.0-beta2-windows-x64.exe) and installed it
on my Windows 7 64 bit system. Installation seemed to go off without a
hitch, but when I tried to link to libpq i
John R Pierce writes:
wild guess says your project is 64 bit, but libpq.dll is 32 bit.
Why would there be a 32bit dll in the 64bit pre-built package?
Regards
Bidski
--
From: "John R Pierce"
Sent: Thursday, July 01, 2010 8:34 AM
To:
Subject: R
On 06/30/10 3:40 PM, Bidski wrote:
John R Pierce writes:
wild guess says your project is 64 bit, but libpq.dll is 32 bit.
Why would there be a 32bit dll in the 64bit pre-built package?
look and see if there's another /lib64/ or similar directory ?
I didn't notice earlier that you are runni
John R Pierce writes:
look and see if there's another /lib64/ or similar directory ?
Nope, no lib64 directory or anything like that, just lib directory.
I didn't notice earlier that you are running the postgres 9 beta.
Yep, Im running PostgreSQL 9.0 beta2
Regards
Bidski
--
Sent via pgsql
12 matches
Mail list logo