| From: | James Robinson <jlrobins(at)socialserve(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, sdv mailer <sdvmailer(at)yahoo(dot)com>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Subject: | Re: PostgreSQL pre-fork speedup |
| Date: | 2004-05-06 19:06:56 |
| Message-ID: | 8B081EC4-9F90-11D8-9C07-000A9566A412@socialserve.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
... too much flushing ...
I agree. I'll bet replacing the pool_write_and_flush() calls in
BinaryRow()
and AsciiRow() with just pool_write(), followed by removing the
fflush() calls at the bottom of those two methods should go a long
way towards fixing things, since the CompleteCommandResponse
handler method ends with a call to pool_write_and_flush(), and
you've pretty much gotta get a CompleteCommand message
trailing all of those rows.
----
James Robinson
Socialserve.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2004-05-06 19:30:59 | Re: PostgreSQL pre-fork speedup |
| Previous Message | Tom Lane | 2004-05-06 19:04:32 | Re: ALTER TABLE TODO items |