| 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 14:28:54 |
| Message-ID: | AM0PR06MB4004E97E28491D84B528976AA7250@AM0PR06MB4004.eurprd06.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>Any changes occur between the time it worked and the time it did not?
>Say a crash, change in schema, new data added and so on.
Not as far as we can tell - one of my DB team noticed it day before yesterday - there were no tell tale signs of any issues but we have seen issues yesterday with certain records not being found
>Per below the version 10 servers use en_GB.UTF_8 and the production one en_US.UTF-8.
>Why the difference?
>And did the production used to be en_GB.UTF_8?
All servers used to be en_US as I think that was the default and had been setup early in our use of PG. I suspect our devops guy corrected this during the upgrade.
>Have you logged into the production instance using psql and tried the queries to see if they work?
Not via psql, but as I said we saw issues from our app layer. I will do a similar test with psql and let you know
Z
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-04-17 14:29:38 | Re: PostgreSQL ping/pong to client |
| Previous Message | Adrian Klaver | 2019-04-17 14:23:40 | Re: Alter domain type / avoiding table rewrite |