Taps seem be dropping the order of indexes

[pupeno]

I have this index in production in Heroku:

CREATE INDEX index_posts_on_blog_id_and_status_and_created_at ON jobs USING btree (blog_id, status, created_at DESC);

and when I download the schema and data with taps, it ends in my local database like this:

CREATE INDEX index_posts_on_blog_id_and_status_and_created_at ON jobs USING btree (blog_id, status, created_at);

the order of created_at was lost.

[will]

heroku db:push and pull will soon be replaced with pg:push and pull, which won't use taps, so it wouldn't have this problem. It'll have all of its own, new problems! If you want a preview check out https://github.com/heroku/heroku-pg-extras/issues/42