| From: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Possible corrupt index? |
| Date: | 2019-04-17 07:42:55 |
| Message-ID: | AM0PR06MB400498ED0A781F3568367FB0A7250@AM0PR06MB4004.eurprd06.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>I am not following above.
>What is running version 10?
Production is 9.6, others are 10 (as we are testing). Prod has always been fine, its been running for 2 years without a hitch. This issue has only occurred recently
>Did you restore a dump from a version 10 onto a >version 9.6 machine?
No - as I said, I don’t believe it’s a version issue as its been fine for 2 years.
>
>> What does:
>> SHOW lc_collate;
>
> en_US.UTF-8
>The above is the same for all the servers?
The upgraded 10 servers are en_GB.UTF_8. The current prod 9.6 is as above
Z
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Kane | 2019-04-17 09:14:51 | Re: Alter domain type / avoiding table rewrite |
| Previous Message | Julie Nishimura | 2019-04-17 05:51:07 | Re: text search configuration missing while migration from 8.3 to 9.4 |