BUG #5487: dblink failed with 63 bytes connection names

From: "Takahiro Itagaki" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5487: dblink failed with 63 bytes connection names
Date: 2010-06-01 02:17:15
Message-ID: 201006010217.o512HFMn057893@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs pgsql-hackers


The following bug has been logged online:

Bug reference: 5487
Logged by: Takahiro Itagaki
Email address: itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp
PostgreSQL version: 9.0beta1
Operating system: Linux
Description: dblink failed with 63 bytes connection names
Details:

Contib/dblink module seems to have a bug in handling
connection names in NAMEDATALEN-1 bytes.

It cannot use exiting connections with 63 bytes name
in some cases. For example, we cannot disconnect
such connections. Also, we can reconnect with the
same name and will have two connections with the name.

=# SELECT dblink_connect(repeat('1234567890', 6) || 'ABC',
'host=localhost');
dblink_connect
----------------
OK
(1 row)

=# SELECT dblink_get_connections();
dblink_get_connections
-------------------------------------------------------------------
{123456789012345678901234567890123456789012345678901234567890ABC}
(1 row)

=# SELECT dblink_disconnect(repeat('1234567890', 6) || 'ABC');
ERROR: connection
"123456789012345678901234567890123456789012345678901234567890ABC" not
available

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-06-01 02:40:35 Re: functional call named notation clashes with SQL feature
Previous Message Florian Pflug 2010-06-01 01:24:26 Re: functional call named notation clashes with SQL feature

Browse pgsql-bugs by date

  From Date Subject
Next Message Takahiro Itagaki 2010-06-01 02:55:11 Re: BUG #5487: dblink failed with 63 bytes connection names
Previous Message Bruce Momjian 2010-05-31 20:36:50 Re: Bug in CREATE FUNCTION with character type (CONFIRMED BUG)