| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> | 
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> | 
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgreSQL(dot)org> | 
| Subject: | Re: Refactoring pgbench.c | 
| Date: | 2015-06-28 06:10:26 | 
| Message-ID: | alpine.DEB.2.10.1506280754280.21612@sto | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Hello Tatsuo,
> Main pgbench logic consists of single file pgbench.c which is 4036 lines 
> of code as of today. This is not a small number and I think it would be 
> nice if it is divided into smaller files because it will make it easier 
> to maintain, add or change features of pgbench.
I do not think that this large file is a so big a problem (good editors 
help navigation in the code), and I'm not sure that splitting it would 
achieve much: there are not that many functions, some of them are maybe 
long (main, threadRun, doCustom) but mostly for good reasons.
I've submitted a patch to remove "fork-emulation", which I think would 
really help simplify the code (maybe -10% source in "pgbench.c", less 
#ifs, avoid double implementations or more-complex-than-necessary 
implementations or not-implemented features).
-- 
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2015-06-28 06:47:05 | Re: proposal: condition blocks in psql | 
| Previous Message | Pavel Stehule | 2015-06-28 06:01:50 | Re: proposal: condition blocks in psql |