Re: PATCH: optimized DROP of multiple tables within a transaction

Tomas Vondra <tv@fuzzy.cz>

From: Tomas Vondra <tv@fuzzy.cz>
To: pgsql-hackers@postgresql.org
Date: 2013-01-17T23:55:05Z
Lists: pgsql-hackers
On 17.1.2013 20:19, Alvaro Herrera wrote:
> 
> I'm curious -- why would you drop tables in groups of 100 instead of
> just doing the 100,000 in a single transaction?  Maybe that's faster
> now, because you'd do a single scan of the buffer pool instead of 1000?
> (I'm assuming that "in groups of" means you do each group in a separate
> transaction)

There's a limited number of locks, and each DROP acquires a lock
(possibly more than one).

Tomas



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Accelerate end-of-transaction dropping of relations