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-08T21:38:52Z
Lists: pgsql-hackers
Attachments
- drop-in-transaction-v8.patch (text/x-diff) patch v8
On 8.1.2013 22:30, Alvaro Herrera wrote: > Tomas Vondra wrote: >> On 8.1.2013 03:47, Shigeru Hanada wrote: > >>>>> * +1 for Alvaro's suggestion about avoiding palloc traffic by starting >>>>> with 8 elements or so. >>>> >>>> Done. >>> >>> Not yet. Initial size of srels array is still 1 element. >> >> I've checked the patch and I see there 'maxrels = 8' - or do you mean >> something else? > > Well, you need to ensure that the initial palloc is an array of that > size. Oh, right - I forgot to modify the palloc() call. Thanks for spotting this. Attached is a patch with increased threshold and fixed palloc call. Tomas
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Accelerate end-of-transaction dropping of relations
- 279628a0a7cf 9.3.0 cited