Ühel kenal päeval, N, 2007-03-22 kell 07:09, kirjutas Andrew Dunstan: > Pavan Deolasee wrote: > > What I am hearing from many users is that its probably not such > > a nice thing to put such restriction. Thats fair. It really helps to think > > about a solution once you know what is acceptable and what is not. > > > That's likely to be the reaction for almost any restriction you can > imagine. Performance improvements are great, but you can't ask people > for whom current performance is adequate to pay a price in functionality > for them.
An easy solution would be to not enable HOT by default, so people who dont want to pay the price of no in-transaction CREATE INDEX for HOT improvements don't have to. > cheers > > andrew > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org -- ---------------- Hannu Krosing Database Architect Skype Technologies OÜ Akadeemia tee 21 F, Tallinn, 12618, Estonia Skype me: callto:hkrosing Get Skype for free: http://www.skype.com ---------------------------(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
