View Single Post

   
  #7 (permalink)  
Old 04-15-2008, 11:28 PM
Gregory Stark
 
Posts: n/a
Default Re: max_prepared_transactions default ... why 5?


"Decibel!" <decibel@decibel.org> writes:

> Actually, the amount of memory is a reason to default to 0, or change the
> name, or put a big comment in the config, because I very often saw databases
> where people had set this to a very high value under the impression that it
> impacted prepared statements.


There's another cost associated with prepared transactions. If it's set to 0
then there's no real reason we need to wal log lock operations.


--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Reply With Quote