Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdj8u-0002ZK-HC for pgsql-bugs@arkaria.postgresql.org; Sat, 14 Nov 2020 00:10:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kdj8t-00072m-9q for pgsql-bugs@arkaria.postgresql.org; Sat, 14 Nov 2020 00:10:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdj8t-00072T-2B for pgsql-bugs@lists.postgresql.org; Sat, 14 Nov 2020 00:10:11 +0000 Received: from mail-pf1-x42d.google.com ([2607:f8b0:4864:20::42d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kdj8q-0006jB-Vb for pgsql-bugs@lists.postgresql.org; Sat, 14 Nov 2020 00:10:10 +0000 Received: by mail-pf1-x42d.google.com with SMTP id b63so5380170pfg.12 for ; Fri, 13 Nov 2020 16:10:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=Cch5od6C64D6DotvF3xYkeW0hCiWxMpUcKFcweqP9/g=; b=kiEabuxjzivdsTHFkq402/Zu4sU4ZOQQJY15SiafxTqVF0LOWoOBugQclOa1kznGit S1apXxqyZvak2UA/eHoms/i7PkicVIknvqyC7p5rQnKCNSrnl7xI+C51MBmVQdKeCpdY uPhdVrH2z8Ws7tFHptXz9xdv7LO4+q2zbB+InSA56mc4e4ZB1xORE+cK5g84Eds4H0ls nawO5WXXdImJU1fVfGj4R1ulwx5VjLhdT+Mo7yyQ+02HP805/ndW8WKgrUw0LSYoQ5qU 9Y/tXss5QsvTuBoNGLVVIskrLTqGr/cZ+i+jT1yZDddZ0SW7g0OfuBtYLaOejrktyQPL 9DZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=Cch5od6C64D6DotvF3xYkeW0hCiWxMpUcKFcweqP9/g=; b=o/G6kTn5Hgs6MAyrSpXEs0f0d5Kec7izNKUETBUbaFkYtfX+BdM+Ww34wLnGn7ML15 0dfXGskI8S8oJq/grYDQdqStOMR4sk5RQhYw2IGl35HWnWr/fS3RMyAbbUAeM5UQPh+w RvRd5nuUQ1fwZSEaLpjP5ROeXggZU3BMyek9inHs3qxy06kzsnY22p7XrQQ5XyebIWSL ijmW+/PA0bw9K06pGc3yxRjwIm/MX46Umb+2YOpQcx1Dz7lbNGiDA+OkW6aF9r+2uGWQ D9eYC42TL1tRRBkqj/cw6bOoPaarwxIIBWwM8uYAA7SvjPT0CnPCl/q+6cm6x/BVxQTg VP5Q== X-Gm-Message-State: AOAM532ugI6ZfaU7ZYXsirfAM60MRHDqKcO++ytLOZ09spIPoztdpK1r 4uZhG9XmFoPJMG14KQokDaW2I8NDY9br7A== X-Google-Smtp-Source: ABdhPJwFKtm11NxEHAsEgqBzJBQy/niD4nW6W16KvFjH1V1Eh5xEW7jmnVmYXpTj6kI3T7tKZ2WGjA== X-Received: by 2002:a63:5143:: with SMTP id r3mr3808579pgl.439.1605312606717; Fri, 13 Nov 2020 16:10:06 -0800 (PST) Received: from vg-db (cpe-108-184-74-100.socal.res.rr.com. [108.184.74.100]) by smtp.gmail.com with ESMTPSA id d22sm3475510pjw.11.2020.11.13.16.10.05 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 Nov 2020 16:10:05 -0800 (PST) Message-ID: <9da8208c61333d155a7328b107f75b85a0bf832e.camel@gmail.com> Subject: Re: PG 9.6.20 -- query misbehaves in replica From: Ernesto =?ISO-8859-1?Q?Hern=E1ndez-Novich?= To: PostgreSQL mailing lists Date: Fri, 13 Nov 2020 16:10:04 -0800 In-Reply-To: References: <9bd869ddbddc71721de1d9d6a2710a1cfec5e98b.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, 2020-11-14 at 00:59 +0100, Magnus Hagander wrote: > On Sat, Nov 14, 2020 at 12:17 AM Ernesto Hernández-Novich < > emhnemhn@gmail.com> wrote: [...] > > After updating from 9.6.19 to 9.6.20, we noticed the query was not > > working on D. [...] > > Looks like a the 9.6.20 over Debian 10 is the culprit, but I have > > nothing else to work on. > > These issues are almost certainly because of the glibc locale changes > between Debian 9 and Debian 10, and not because of the PostgreSQL > upgrade. > > If you have master and standby on different glibc versions (so debian > 9 vs 10), all text based indexes can behave differently. All the > nodes must run the same version for this to work. So in this > scenario, you need to reinstall B and D with debian 9, or you need to > upgrade your other nodes to debian 10 (and if you do that, then you > have to reindex the master node once it has been upgraded). I agree on the locale matching and will try your suggestion. I must say the Debian 10 machines were working just fine with PG 9.6.19 for over two months or so. We noticed the issue *just* this week after upgrading from 9.6.19 onto 9.6.20. Regards, -- Ernesto Hernández-Novich - @iamemhn - Unix: Live free or die! Geek by nature, Linux by choice, Debian of course. If you can't aptitude it, it isn't useful or doesn't exist. GPG Key Fingerprint = 0064 ADF5 EB5C DE16 99C1 6C56 F2A3 86B5 A757 E5A1