pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Marc Millas <marc.millas@mokadb.com>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: order by
Date: Thu, 11 May 2023 07:43:17 -0700
Message-ID: <0f2ae006-12a0-41d4-d41e-4b2cf6f4e744@aklaver.com> (raw)
In-Reply-To: <CADX_1ab4n123_T4N_mkHEBO1uPVh2i2bzXoo7pzPJknxWJP1dw@mail.gmail.com>
References: <CADX_1ab4n123_T4N_mkHEBO1uPVh2i2bzXoo7pzPJknxWJP1dw@mail.gmail.com>

On 5/11/23 07:29, Marc Millas wrote:
> Hi,
> 
> I keep on investigating on the "death postgres" subject
> but open a new thread as I don't know if it's related to my pb.
> 
> I have 2 different clusters, on 2 different machines, one is prod, the 
> second test.
> Same data volumes.

How can they be sharing the same data 'volume'?

Do you mean you are doing dump/restore between them?

Postgres version for each cluster is?

> 
> On prod if I do
> select col_a, count(col_a) from table_a group by col_a order by col_a desc,
> I get the numbers of NULL on top.
> To get the number of NULL on top on the test db, I have to
> select col_a, count(col_a) from table_a group by col_a order by col_a asc.
> 
> so, it looks like there is something different within the b-tree 
> operator class of varchar (?!?)
> between those 2 clusters.
> 
> What can I check to to explain this difference as, to my understanding, 
> it's not a postgresql.conf parameter.
> 
> thanks
> 
> Marc MILLAS
> Senior Architect
> +33607850334
> www.mokadb.com <http://www.mokadb.com;
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (27+ messages)  latest in thread

Message-ID: <0f2ae006-12a0-41d4-d41e-4b2cf6f4e744@aklaver.com>
Permalink:  ../0f2ae006-12a0-41d4-d41e-4b2cf6f4e744@aklaver.com/
Also on:    postgresql.org/message-id/0f2ae006-12a0-41d4-d41e-4b2cf6f4e744@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, marc.millas@mokadb.com
  Subject: Re: order by
  In-Reply-To: <0f2ae006-12a0-41d4-d41e-4b2cf6f4e744@aklaver.com>
  References: <CADX_1ab4n123_T4N_mkHEBO1uPVh2i2bzXoo7pzPJknxWJP1dw@mail.gmail.com> <0f2ae006-12a0-41d4-d41e-4b2cf6f4e744@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox