Re: Lc_collate & lc_type? whitespace and nbsp unique index... - Mailing list pgsql-admin

From Ilmir Mulyukov
Subject Re: Lc_collate & lc_type? whitespace and nbsp unique index...
Date
Msg-id CAGiHuoWSHBB3hnOeJD42xnuvUT3KvqJRK6Fc_KZ6ndcYi925Uw@mail.gmail.com
Whole thread Raw
In response to Re: Lc_collate & lc_type? whitespace and nbsp unique index...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
I assumed that the issue with the module which implements the mchar and mvarchar types...
Thank you, Laurenz and Tom for your help.


вт, 13 июл. 2021 г., 23:43 Tom Lane <tgl@sss.pgh.pa.us>:
Ilmir Mulyukov <ilmir.mulyukov@gmail.com> writes:
> Laurenz, there is no index for this table.
> ka_im_pg=# \d _inforg31440
>                   Table "public._inforg31440"
>     Column     |     Type      | Collation | Nullable | Default
> ---------------+---------------+-----------+----------+---------
>  _fld31441     | mvarchar(400) |           | not null |
>  _fld31442     | mvarchar(10)  |           | not null |
>  _fld31443rref | bytea         |           | not null |
>  _fld2102      | numeric(7,0)  |           | not null |

What in the world is type "mvarchar"?  It's certainly not
anything defined by core Postgres.  I think you need to
address this question to whoever wrote that datatype.
It seems somewhat likely that this is intentional behavior
for the type.

                        regards, tom lane

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Lc_collate & lc_type? whitespace and nbsp unique index...
Next
From: Matti Linnanvuori
Date:
Subject: Re: Upgrade postgresql