| From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Log timings on Windows 64 |
| Date: | 2009-07-20 19:01:07 |
| Message-ID: | d3ab2ec80907201201x5659908ey75705d512f0ecc5c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hey all,
I'm looking at windows, and a couple of quick google's didn't give me
anything,
If I set my log_min_duration_statement < 16 ms, I get one of 2 values
for my pgbench runs (pretty quick statements). 0, or 16 ms (sometimes
15.999). If I benchmark some other way (via my app) things look the same.
If I set my log_line_prefix to %m vs. %t, then the time increments in 16ms
chunks. I'm guessing this is an OS limitation on windows. Does anybody
else have experience here (or aware of a previous bug)?
Thanks
--Scott
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CG | 2009-07-20 19:09:07 | Re: best practice transitioning from one datatype to another |
| Previous Message | Joshua D. Drake | 2009-07-20 18:09:46 | Re: suggestion: log_statement = sample |