Re: idea for concurrent seqscans - Mailing list pgsql-hackers

From Neil Conway
Subject Re: idea for concurrent seqscans
Date
Msg-id 42216066.6090208@samurai.com
Whole thread Raw
In response to Re: idea for concurrent seqscans  (Jeff Davis <jdavis-pgsql@empires.org>)
List pgsql-hackers
Jeff Davis wrote:
> The only reason I did that was because the original source was difficult
> to read and work on. Is there a reason that code and comments wrap
> around to the next line throughout the file?

I'm not sure what you mean. Assuming your editor expand tabs to 4 spaces 
(which is the convention in the PostgreSQL source), lines should be 
about 80 characters at most. Expressions that would take more characters 
horizontally if left on one line are divided into multiple lines, and 
indented appropriately. At any rate, the source is perfectly readable to 
me :) Perhaps you need to tweak your editor's configuration?

-Neil


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: win32 performance - fsync question
Next
From: "Magnus Hagander"
Date:
Subject: Re: win32 performance - fsync question