From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ilmir Mulyukov <ilmir(dot)mulyukov(at)gmail(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Lc_collate & lc_type? whitespace and nbsp unique index... |
Date: | 2021-07-13 17:43:32 |
Message-ID: | 3278464.1626198212@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ilmir Mulyukov <ilmir(dot)mulyukov(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ilmir Mulyukov | 2021-07-14 03:47:58 | Re: Lc_collate & lc_type? whitespace and nbsp unique index... |
Previous Message | Ilmir Mulyukov | 2021-07-13 15:57:58 | Re: Lc_collate & lc_type? whitespace and nbsp unique index... |