Hi Tom,
that's very useful information. Very cool to get such results so quickly here.
Thanks
Maik
> Am 20.05.2015 um 16:05 schrieb Tom Lane :
>
> Adrian Klaver writes:
>> The reason I ask is that the machine you are having problems with has OS
>> X. Over the years I have seen quite a few re
Adrian Klaver writes:
> The reason I ask is that the machine you are having problems with has OS
> X. Over the years I have seen quite a few reports on this list of OS X
> locale/encoding issues.
Yes. Here's the problem: OS X UTF8 locales (other than C) don't sort the
same as UTF8 locales on L
On 05/20/2015 06:34 AM, Musall Maik wrote:
Am 20.05.2015 um 15:17 schrieb Adrian Klaver :
On 05/19/2015 11:52 PM, Musall Maik wrote:
Hi,
I have a strange case where a SELECT for a primary key returns 0 rows on one
slave, while it returns the correct 1 row on another slave and on the master.
> Am 20.05.2015 um 15:17 schrieb Adrian Klaver :
>
> On 05/19/2015 11:52 PM, Musall Maik wrote:
>> Hi,
>>
>> I have a strange case where a SELECT for a primary key returns 0 rows on one
>> slave, while it returns the correct 1 row on another slave and on the
>> master. It does however return t
On 05/19/2015 11:52 PM, Musall Maik wrote:
Hi,
I have a strange case where a SELECT for a primary key returns 0 rows on one
slave, while it returns the correct 1 row on another slave and on the master.
It does however return that row on all slaves when queried with LIKE and
trailing or leadin
Hi Melvin,
thanks for the response.
> Am 20.05.2015 um 14:26 schrieb Melvin Davidson :
>
> First, are your postgresql.conf options the same on master and slave2 with
> regard to memory allocation and all Planner Method Configuration options?
slave2 has less shared_buffers (256m vs 2048m), temp
First, are your postgresql.conf options the same on master and slave2 with
regard to memory allocation and all Planner Method Configuration options?
Next, is it possible you have a corrupted index on slave2.?
I would suggest verifying there is no difference in the query plan between
master and sl
Hi,
I have a strange case where a SELECT for a primary key returns 0 rows on one
slave, while it returns the correct 1 row on another slave and on the master.
It does however return that row on all slaves when queried with LIKE and
trailing or leading wildcard.
psql version is 9.3.5, because t
