vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| If I turn on stats_command_string, how much impact would it have on PostgreSQL server's performance during a period of massive data INSERTs? I know that the answer to the question I'm asking will largely depend upon different factors so I would like to know in which situations it would be negligible or would have a signifcant impact. |
| ||||
| On Thu, Oct 20, 2005 at 01:33:07PM -0700, jnevans@gmail.com wrote: > If I turn on stats_command_string, how much impact would it have on > PostgreSQL server's performance during a period of massive data > INSERTs? Do you really need to be doing "massive data INSERTs"? Can you use COPY, which is much more efficient for bulk loads? http://www.postgresql.org/docs/8.0/i.../populate.html -- Michael Fuhr ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |