From: | M Sarwar <sarwarmd02(at)outlook(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(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-15 17:16:53 |
Message-ID: | DM4PR19MB5978A5CC04E91426AB4E7782D35BA@DM4PR19MB5978.namprd19.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-advocacy |
Yes, This is what I am understanding.
I am in the database administration for couple of decades but never realized this intricacies.
Probably this is more known in the development side. I am learning now 🙂
Thank you,
________________________________
From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Sent: Wednesday, June 14, 2023 6:54 PM
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
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 | M Sarwar | 2023-06-15 17:26:28 | Re: The same result for with SPACE and without SPACE |
Previous Message | M Sarwar | 2023-06-15 17:13:10 | Re: The same result for with SPACE and without SPACE |
From | Date | Subject | |
---|---|---|---|
Next Message | M Sarwar | 2023-06-15 17:26:28 | Re: The same result for with SPACE and without SPACE |
Previous Message | M Sarwar | 2023-06-15 17:13:10 | Re: The same result for with SPACE and without SPACE |