| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Mixed Locales and Upgrading |
| Date: | 2020-03-22 21:48:57 |
| Message-ID: | CAHJZqBBPf_peA40ZswtcYaj5OA0OxynJxKqVs57sARzEe45QtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 17, 2020 at 9:25 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> There is no way to know how much indexes would get broken without
> having a look at it. Anything ASCII-based should be of no problem.
> If you have a doubt, reindexing evey index which includes text column
> data is the best course of action in my opinion if you have any
> doubts, because that's safe even if it has a higher cost.
>
Here's the fun part. A lot of the tables use UUIDv4 strings for primary
keys. However these are stored in text/varchar columns.
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pabloa98 | 2020-03-22 21:53:58 | Re: Could postgres12 support millions of sequences? (like 10 million) |
| Previous Message | Matt Magoffin | 2020-03-22 21:48:00 | Re: Duplicate key violation on upsert |