Re: Possible corrupt index? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Possible corrupt index?
Date
Msg-id cec697e9-44aa-f567-2d71-7a323c8e8d37@aklaver.com
Whole thread Raw
In response to RE: Possible corrupt index?  (Zahir Lalani <ZahirLalani@oliver.agency>)
List pgsql-general
On 4/17/19 7:28 AM, Zahir Lalani wrote:
> 
>> 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
issuesbut we have seen issues yesterday with certain records not being found
 

Does that including looking at the logs?

> 
>> 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
devopsguy corrected this during the upgrade.
 

Did that extend to fiddling with the locale on the production machine?

> 
>> 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
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL ping/pong to client
Next
From: Ajay Pratap
Date:
Subject: Re: PostgreSQL ping/pong to client