Request a Demo
Home   >   mailing lists

Re: length coerce for bpchar is broken since 7.0 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: length coerce for bpchar is broken since 7.0
Date
Msg-id 28919.971752781@sss.pgh.pa.us
Whole thread Raw
In response to length coerce for bpchar is broken since 7.0  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: length coerce for bpchar is broken since 7.0
List pgsql-hackers
Tree view 
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> If VARSIZE returned from exprTypmod() and atttypmod passed to
> coerce_type_typmod() is equal, the function node to call bpchar()
> would not be added.

Um, what's wrong with that?  Seems to me that parse_coerce is doing
exactly what it's supposed to, ie, adding only length coercions
that are needed.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: length coerce for bpchar is broken since 7.0
Next
From: Bruce Momjian
Date:
Subject: Re: psql's \d functions broken for views in current sources