| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Igor Korot <ikorot01(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to properly use TRIM()? |
| Date: | 2026-03-07 14:29:48 |
| Message-ID: | CAKFQuwZLKOCBMpk+xK8=0paNpBK1juBhyO=MghqFu84cTnSzEw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday, March 7, 2026, Igor Korot <ikorot01(at)gmail(dot)com> wrote:
> '
> name | tablespace | included | storage
> --------------+------------+----------+---------
> leagues_pkey | | {} |
> (1 row)
>
> Included is one, storage is not.
>
That’s a terrible way to determine the data type of a column.
Did read the error message you were given? Did you read the documentation?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2026-03-07 15:44:30 | Re: How to properly use TRIM()? |
| Previous Message | Tom Lane | 2026-03-07 11:45:29 | Re: Unexpected deadlock across two separate rows, using Postgres 17 and Django's select_for_update() |