From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Michal Novotny <michal(dot)novotny(at)trustport(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Question about DROP TABLE |
Date: | 2016-01-12 11:01:30 |
Message-ID: | CAFj8pRCWbVhOfeyf9Gfd2sGSbq4+3Q1DB=2wktpggyQumeFR9Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
2016-01-12 11:57 GMT+01:00 Michal Novotny <michal(dot)novotny(at)trustport(dot)com>:
> Dear PostgreSQL Hackers,
> I've discovered an issue with dropping a large table (~5T). I was
> thinking drop table is fast operation however I found out my assumption
> was wrong.
>
> Is there any way how to tune it to drop a large table in the matter of
> seconds or minutes? Any configuration variable in the postgresql.conf or
> any tune up options available?
>
drop table should be fast.
There can be two reasons why not:
1. locks - are you sure, so this statement didn't wait on some lock?
2. filesystem issue - can you check the speed of rm 5TB file on your IO?
Regards
Pavel
>
> PostgreSQL version used is PgSQL 9.4.
>
> Thanks a lot!
> Michal
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-01-12 11:05:04 | Re: Question about DROP TABLE |
Previous Message | Michal Novotny | 2016-01-12 10:57:05 | Question about DROP TABLE |