Re: Order by and timestamp

From: Björn Lundin <b(dot)f(dot)lundin(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Order by and timestamp
Date: 2020-03-16 08:51:51
Message-ID: 7D74B8B5-DFBD-4B5B-85C6-A516343E49C1@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 16 mars 2020 kl. 01:41 skrev Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> On 3/15/20 2:33 PM, Björn Lundin wrote:
>>> I then did ’select * from AMARKETS order by STARTTS’
>
>> Is amarkets in more then one schema?
>
> Yeah, it's hard to think of any explanation other than "the query used a
> corrupt index on startts to produce the ordering". But your \d doesn't
> show any index on startts. So maybe there's more than one amarkets
> table?

Yes - in other schemas - described in reply to Adrain
But the schema_path does not point to them
And those two other tables are empty

> Another possibly-useful bit of evidence is to see what EXPLAIN shows as
> the query plan for this query.

bnl=> explain select * from amarkets order by startts;
QUERY PLAN
-----------------------------------------------------------------------
Sort (cost=10702.57..10939.29 rows=94691 width=106)
Sort Key: startts
-> Seq Scan on amarkets (cost=0.00..2875.91 rows=94691 width=106)
(3 rader)

--
Björn Lundin
b(dot)f(dot)lundin(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nicola Contu 2020-03-16 09:57:11 Re: Streaming replication - 11.5
Previous Message Björn Lundin 2020-03-16 08:49:23 Re: Order by and timestamp