From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | M Sarwar <sarwarmd02(at)outlook(dot)com> |
Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: The same result for with SPACE and without SPACE |
Date: | 2023-06-14 22:54:50 |
Message-ID: | B92B919F-8A47-48F5-BD5C-4C125A2E6F79@elevated-dev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-advocacy |
One more followup comment: CHAR is rather an archaic vestige, from a time when fixed-length vs variable-length might measurably improve performance somewhere, or removing the requirement to store a length with every instance might help with space requirements. There is really almost no anymore to ever use it for fixed length strings. There is *NO* good reason that I know of to ever use it for values which are not actually fixed-length, that is assuredly a mistake.
From | Date | Subject | |
---|---|---|---|
Next Message | Wetmore, Matthew (CTR) | 2023-06-15 13:08:06 | The same result for with SPACE and without SPACE |
Previous Message | Scott Ribe | 2023-06-14 22:47:21 | Re: The same result for with SPACE and without SPACE |
From | Date | Subject | |
---|---|---|---|
Next Message | Wetmore, Matthew (CTR) | 2023-06-15 13:08:06 | The same result for with SPACE and without SPACE |
Previous Message | Scott Ribe | 2023-06-14 22:47:21 | Re: The same result for with SPACE and without SPACE |