Re: PostgreSQL pre-fork speedup - Mailing list pgsql-hackers

From James Robinson
Subject Re: PostgreSQL pre-fork speedup
Date
Msg-id 8B081EC4-9F90-11D8-9C07-000A9566A412@socialserve.com
Whole thread Raw
In response to Re: PostgreSQL pre-fork speedup  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER TABLE TODO items
Next
From: "scott.marlowe"
Date:
Subject: Re: PostgreSQL pre-fork speedup