Re: [PERFORM] ORDER BY performance deteriorates very quickly as dataset grows

Add column job_id to translation table and create index on job_id an translation_id columns -- View this message in context: http://postgresql.1045698.n5.nabble.com/ORDER-BY-performance-deteriorates-very-quickly-as-dataset-grows-tp5776965p5776974.html Sent from the PostgreSQL - performance mai

Re: [PERFORM] ORDER BY performance deteriorates very quickly as dataset grows

I suggest to use denormalization, add column job_id to translation table -- View this message in context: http://postgresql.1045698.n5.nabble.com/ORDER-BY-performance-deteriorates-very-quickly-as-dataset-grows-tp5776965p5776973.html Sent from the PostgreSQL - performance mailing list archive at

Re: [PERFORM] Query completed in < 1s in PG 9.1 and ~ 700s in PG 9.2

Please try LIMIT 1 in exists exists(select id from condition_document_excerpt where condition_id=c1686.id LIMIT 1) as v1686_has_reference -- View this message in context: http://postgresql.1045698.n5.nabble.com/Query-completed-in-1s-in-PG-9-1-and-700s-in-PG-9-2-tp5730899p5731021.html Sent fro