Re: [BUGS] BUG #5487: dblink failed with 63 bytes connection names - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: [BUGS] BUG #5487: dblink failed with 63 bytes connection names
Date
Msg-id 20100603100753.931D.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: [BUGS] BUG #5487: dblink failed with 63 bytes connection names  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:

> Well, looking at the callers, most if not all of them seem to actually
> pass a palloc'd copy, allocated by text_to_cstring().
>
> Should we throw a NOTICE like vanilla truncate_identifier() does?
>
> I feel it would be better to just call truncate_identifier() than roll
> your own. Assuming we want the same semantics in dblink, we'll otherwise
> have to remember to update truncate_identifier_copy() with any changes
> to truncate_identifier().

That makes sense. Now I use truncate_identifier(warn=true) for the fix.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center


Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: ALTER TABLE .... make constraint DEFERRABLE
Next
From: Florian Pflug
Date:
Subject: Re: recovery getting interrupted is not so unusual as it used to be