| From: | Rui DeSousa <rui(at)crazybean(dot)net> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | raf <raf(at)raf(dot)org>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| Date: | 2020-04-29 00:40:57 |
| Message-ID: | 6404DFBD-2864-473E-8807-C95D35C6C715@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
> On Apr 28, 2020, at 8:34 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> Its less problematic now that increasing the generally arbitrary length doesn't require a table rewrite but you still need to rebuild dependent objects.
>
To increase a column length does not require a table rewrite or table scan; however, reducing its size will require a full table scan. So cleaning up a schema like the one proposed sucks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-04-29 01:22:42 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| Previous Message | David G. Johnston | 2020-04-29 00:34:00 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-04-29 00:47:10 | Re: [HACKERS] Restricting maximum keep segments by repslots |
| Previous Message | Andy Fan | 2020-04-29 00:34:59 | Re: [PATCH] Keeps tracking the uniqueness with UniqueKey |