| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rui DeSousa <rui(at)crazybean(dot)net> |
| 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 01:22:42 |
| Message-ID: | CAKFQuwZpiNNtfn6oqkdWXXBVjOXdz6nZQZTxnRhJSzQBRqhwTQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Tue, Apr 28, 2020 at 5:40 PM Rui DeSousa <rui(at)crazybean(dot)net> wrote:
> 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.
>
I estimate the probability of ever desiring to reduce the length of a
varchar field to be indistinguishable from zero.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raf | 2020-04-29 02:29:28 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| Previous Message | Rui DeSousa | 2020-04-29 00:40:57 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2020-04-29 02:03:53 | Re: Avoiding hash join batch explosions with extreme skew and weird stats |
| Previous Message | Alvaro Herrera | 2020-04-29 00:47:10 | Re: [HACKERS] Restricting maximum keep segments by repslots |