No need to document drop_table in the PostgreSQLAdapter

It behaves in the same way that the abstract adapter.

[ci skip]

1 files changed, 1 insertions, 9 deletions

diff --git a/activerecord/lib/active_record/connection_adapters/postgresql/schema_statements.rb b/activerecord/lib/active_record/connection_adapters/postgresql/schema_statements.rb
index 44781125ae..168180cfd3 100644
--- a/activerecord/lib/active_record/connection_adapters/postgresql/schema_statements.rb
+++ b/activerecord/lib/active_record/connection_adapters/postgresql/schema_statements.rb
@@ -87,15 +87,7 @@ module ActiveRecord
           SQL
         end
 
-        # Drops a table from the database.
-        #
-        # [<tt>:force</tt>]
-        #   Set to +:cascade+ to drop dependent objects as well.
-        #   Defaults to false.
-        # [<tt>:if_exists</tt>]
-        #   Set to +true+ to only drop the table if it exists.
-        #   Defaults to false.
-        def drop_table(table_name, options = {})
+        def drop_table(table_name, options = {}) # :nodoc:
           execute "DROP TABLE#{' IF EXISTS' if options[:if_exists]} #{quote_table_name(table_name)}#{' CASCADE' if options[:force] == :cascade}"
         end