you want to place the columns frequently changes on your index if you are creating 'Unique' index. The existing indexing scheme will work just fine, since you have a multiple column index. The likelihood of being all those similar is close to none. So, do not change it.
-apu --- Dmitriy Milashenko <[EMAIL PROTECTED]> wrote: > Hi, freeradius-users. > > I'm using Aqua Gatekeeper to manage voip services. > It makes accounting to sql. > I've used > src/billing/cisco_h323_db_schema-postgres.sql to > create > tables. Table stopvoip have index > > create UNIQUE index stopvoipcombo on stopvoip > (h323SetupTime, nasipaddress, CallID); > > but aqua sends answer and originate accounting > records between 2 > different clients with the same h323SetupTime. So > the second row can > not be inserted into the database... > > So the question... Will it be safely to modify this > index like > > create UNIQUE index stopvoipcombo on stopvoip > (h323SetupTime, > nasipaddress, CallID, h323callorign); > -- > Thank you, > Dmitriy > mailto:[EMAIL PROTECTED] > > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > --------------------------- Before God we are all equally wise - and equally foolish. -Albert Einstein __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
