| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "david(at)calascibetta(dot)com" <david(at)calascibetta(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17258: Unexpected results in CHAR(1) data type |
| Date: | 2021-10-29 18:47:57 |
| Message-ID: | CAKFQuwboTpMgcX6jDweFqndMeJ84XU8o_4UE_pViOAFOE7isvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Friday, October 29, 2021, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17258
> Logged by: David Calascibetta
> Email address: david(at)calascibetta(dot)com
> PostgreSQL version: 12.8
> Operating system: AWS RDS
> Description:
>
> My understanding is that a CHAR(1) column can never be 0 (zero) length.
https://wiki.postgresql.org/wiki/Don%27t_Do_This#Don.27t_use_char.28n.29
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-10-29 18:50:32 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | Peter Geoghegan | 2021-10-29 18:45:34 | Re: BUG #17245: Index corruption involving deduplicated entries |