As we rebuild the whole db now every time we relase a new version, the updated column values are all the same (start time of the transaction: we could in principle switch to statement_timestamp() or clock_timestamp() but that would just give us the same order as pk).
Dropping it from the order_by halves the query time for http://glottolog.org/langdoc on my installation (order stays the same).
As we rebuild the whole db now every time we relase a new version, the
updatedcolumn values are all the same (start time of the transaction: we could in principle switch tostatement_timestamp()orclock_timestamp()but that would just give us the same order aspk).Dropping it from the
order_byhalves the query time for http://glottolog.org/langdoc on my installation (order stays the same).