From aef809f90cf9fda0bc2d7337a2e1c61d69b8e621 Mon Sep 17 00:00:00 2001
From: Ramiro Morales <cramm0@gmail.com>
Date: Sun, 22 Sep 2013 11:11:02 -0300
Subject: [PATCH] [1.6.x] Reference Meta.index_together in DB performance
 guide.

9dc45efeba from master.
---
 docs/topics/db/optimization.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/topics/db/optimization.txt b/docs/topics/db/optimization.txt
index cca2e6381b..a4d90bed5e 100644
--- a/docs/topics/db/optimization.txt
+++ b/docs/topics/db/optimization.txt
@@ -38,7 +38,9 @@ Use standard DB optimization techniques
 
 * Indexes. This is a number one priority, *after* you have determined from
   profiling what indexes should be added. Use
-  :attr:`django.db.models.Field.db_index` to add these from Django.
+  :attr:`django.db.models.Field.db_index` or
+  :attr:`Meta.index_together <django.db.models.Options.index_together>` to add
+  these from Django.
 
 * Appropriate use of field types.