Re: dblink versus long connection strings

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: dblink versus long connection strings
Date: 2010-11-25 09:58:53
Message-ID: AANLkTi=55mHUAgui37mHaLUwSU3ZThmWnSYru6_4-PbG@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 23, 2010 at 02:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> In any case I don't see an argument why warning on connection creation
> isn't sufficient.

I'll check all versions of dblink. truncate_identifier() will be called
with warn=false in all cases except dblink_coneect() -> createNewConnection().

--
Itagaki Takahiro

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-25 10:52:08 Re: GiST insert algorithm rewrite
Previous Message pasman pasmański 2010-11-25 09:57:26 Re: function(contants) evaluated for every row