Hi.
Umm...
If possible, please set up Debug by odbc.ini, and send me /tmp/mylog_xxx999.log.
Regards,
Hiroshi Saito
From: "Unicode converter buffer overflow in psqlodbc driver"
<[EMAIL PROTECTED]>
The following bug has been logged online:
Bug reference: 3601
Logged by: Unico
Hi.
I think that the problem's clarifying path and encoding need to be directed.
Please see,
http://winpg.jp/~saito/pg_work/LageObject_psql.png
Sorry it is japanese:-)
Regards,
Hiroshi Saito
- Original Message -
From: "Pascal Van De Gucht" <[EMAIL PROTECTED]>
The following bug has
=?UTF-8?B?IkzDoXN6bMOzLVLDs2JlcnQsIEFsYmVydCI=?= <[EMAIL PROTECTED]> writes:
> [ ILIKE fails to match case-insensitively in 8.1.2 ]
The ILIKE code doesn't work well at all in multibyte encodings in 8.1
and before. You should get reasonable results in one of the LATINn
encodings (and a matching lo
On Thu, 2007-09-06 at 12:43 +0200, hubert depesz lubaczewski wrote:
> steps to reproduce:
> session1: connect using user1 to database1.
> session2: connect using user2 to database2.
> session1: create table x ( y int);
> session2: begin;
> session1: create index concurrently q on x(y);
> it hangs.
On Thu, 2007-09-06 at 15:55 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Thu, 2007-09-06 at 12:43 +0200, hubert depesz lubaczewski wrote:
> >> i dont really see why this would be neccessary - i understand that we
> >> need to wait for transactions in the same db, but wait
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Thu, 2007-09-06 at 12:43 +0200, hubert depesz lubaczewski wrote:
>> i dont really see why this would be neccessary - i understand that we
>> need to wait for transactions in the same db, but waiting for
>> transaction in another database?
> Manual says
The following bug has been logged online:
Bug reference: 3604
Logged by: Pascal Van De Gucht
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows 2003
Description:lo_import does not work with filenames with accents
Details:
When I use t
On Thu, 2007-09-06 at 12:43 +0200, hubert depesz lubaczewski wrote:
> steps to reproduce:
> session1: connect using user1 to database1.
> session2: connect using user2 to database2.
> session1: create table x ( y int);
> session2: begin;
> session1: create index concurrently q on x(y);
> it hangs.
"Luiz K. Matsumura" <[EMAIL PROTECTED]> writes:
> Description:Strange behaviour of character columns in select with
> views
I've applied a fix for this in CVS HEAD (8.3-to-be), but it seems
impractical to fix it in 8.2 (or 8.1 which also has the issue).
The problem is that when "null::char
The following bug has been logged online:
Bug reference: 3603
Logged by: Jayaram R
Email address: [EMAIL PROTECTED]
PostgreSQL version: 1.6.3
Operating system: Windows ME
Description:ADO PostgreSQL OLE DB Provider ERROR
Details:
i am using postgresSql in Windows ME.
The following bug has been logged online:
Bug reference: 3602
Logged by: Jayaram R
Email address: [EMAIL PROTECTED]
PostgreSQL version: 1.6.3
Operating system: Windows Me
Description:DO PostgreSQL OLE DB Provider
Details:
I am using postgresSql in Windows. And it is
Hi
I have a problem related to the encoding. Maybe this is not the right
place to ask for help, in this case please tell me where to ask for
help.
database version: PostgreSQL 8.1.2 on i686-pc-linux-gnu, compiled by
GCC gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
The problem is the following:
I have
steps to reproduce:
session1: connect using user1 to database1.
session2: connect using user2 to database2.
session1: create table x ( y int);
session2: begin;
session1: create index concurrently q on x(y);
it hangs.
session2: rollback/commit;
session1: finishes.
i dont really see why this would b
The following bug has been logged online:
Bug reference: 3601
Logged by: Unicode converter buffer overflow in psqlodbc driver
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Solaris Sparc V9 32bit
Description:When we try to connect to post
Decibel! wrote:
> Version 1.6.3; if you have a table in public called pg_class and try to
> drop it, pgAdmin gives an error:
>
> ERROR: permission denied: "pg_class" is a system catalog
>
> The drop does work correctly from psql...
I'm sure you (Jim) have seen the reasons why this happens pgAdmi
15 matches
Mail list logo