BUG #5761: In 'dblink' function connection string truncated

"dp" <prikotov@gmail.com> writes:

Description: In 'dblink' function connection string truncated
Details:

The connection info string in 'dblink' function truncated to 62 characters.
On execution: 'NOTICE: identifier "dbname=somebase host=xx.xxx.xx.xx
user=iamuser password=somepassword77 port=5432" will be truncated to
"dbname=somebase host=xx.xxx.xx.xx user=iamuser password=somepas"'

Does this actually break anything, or is it just an annoying NOTICE?
When I try it here, I get the NOTICE as described, but the connection
string still works.

regards, tom lane

Yes, it causes an error for me since it truncates the connection string in
the middle of the username, omitting the password altogether. I must be
missing something; I can't understand what my alternative is but to call the
dblink(text,text) function with a connection string and a SQL statement.

--
View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-5761-In-dblink-function-connection-string-truncated-tp3275060p3284606.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

On Nov 29, 10:50 am, d...@authentrics.com (queej) wrote:

Yes, it causes an error for me since it truncates the connection string in
the middle of the username, omitting the password altogether.  I must be
missing something; I can't understand what my alternative is but to call the
dblink(text,text) function with a connection string and a SQL statement.

I should have mentioned that my dblink() calls are within views, so I
cannot do a two-step process of dblink_connect() followed by a
dblink().

queej <dqj@quinn-jacobs.org> writes:

On Nov 29, 10:50�am, d...@authentrics.com (queej) wrote:

Yes, it causes an error for me since it truncates the connection string in
the middle of the username, omitting the password altogether. �I must be
missing something; I can't understand what my alternative is but to call the
dblink(text,text) function with a connection string and a SQL statement.

I should have mentioned that my dblink() calls are within views, so I
cannot do a two-step process of dblink_connect() followed by a
dblink().

As far as our investigation could tell, the message you're complaining
about is simply a warning and would not result in any actual failure.
I agree it's a bug that the message comes out at all, but it appears
to be just cosmetic. If you have a situation where it leads to a
non-cosmetic problem, you need to provide a complete test case
illustrating that, or it's not going to get fixed.

regards, tom lane