Re: PATCH: optimized DROP of multiple tables within a transaction - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PATCH: optimized DROP of multiple tables within a transaction
Date
Msg-id CA+TgmoaVQckAJ6GbRW4OOPV4oQm-NGW+EYt=VVyqVD9qTXi+LQ@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: optimized DROP of multiple tables within a transaction  (Tomas Vondra <tv@fuzzy.cz>)
Responses Re: PATCH: optimized DROP of multiple tables within a transaction
List pgsql-hackers
On Mon, Dec 31, 2012 at 11:51 AM, Tomas Vondra <tv@fuzzy.cz> wrote:
> I thought I followed the conding style - which guidelines have I broken?

+    /* If there are no non-local relations, then we're done. Release the memory
+     * and return. */

Multi-line comments should start with a line containing only /* and
end with a line containing only */.

+DropRelFileNodeAllBuffers(RelFileNodeBackend * rnodes, int nnodes)
and
+rnode_comparator(const void * p1, const void * p2)

The extra spaces after the asterisks should be removed.

+void smgrdounlinkall(SMgrRelation * rels, int nrels, bool isRedo)
+{

void should be on a line by itself.

Sorry to nitpick.

As for BSEARCH_LIMIT, I don't have a great idea - maybe just
DROP_RELATIONS_BSEARCH_LIMIT?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Next
From: Tom Lane
Date:
Subject: Re: lock AccessShareLock on object 0/1260/0 is already held