Thanks, done. ---------------------------------------------------------------------------
Alvaro Herrera wrote: > Jim C. Nasby wrote: > > On Tue, Sep 19, 2006 at 09:37:39AM -0400, Bruce Momjian wrote: > > > Jim C. Nasby wrote: > > > > On Mon, Sep 18, 2006 at 06:47:02PM -0400, Bruce Momjian wrote: > > > > > > Both this and pg_prepared_statements are very useful for pooled > > > > > > connection setups." > > > > > > > > > > > > Should read "Both of these are very useful..." > > > > > > > > > > I don't think I can't change that because they are two separate bullet > > > > > items. > > > > > > > > Except it's refering to both items. Maybe the two items should just be > > > > combined into one? > > > > > > Please post some combined wording, but I am afraid it will be too > > > complicated to merge them. > > > > - Add pg_prepared_statements and pg_cursors system views to show prepared > > statements and open cursors. > > > > Both of these are very useful for pooled connection setups. > > - Add pg_prepared_statements ... > > - Add pg_cursors ... > This, and pg_prepared_statements above, are both useful for ... > > -- > Alvaro Herrera http://www.CommandPrompt.com/ > PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(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