Re: postgres performance issues

Mon, 18 Aug 2003 10:02:31 -0700

I will be looking at the postgres accounting in freeradius very closely soon, since I have been asked to move to freeradius from cistron. I modified cistron to account to postgres and have solved the problems associated with duplicate records. By setting up the primary key over a set of attributes, any duplicate records inserts would be rejected and then I insert that record into a table for duplicates {ie: acct_dups_2003aug}. I have also added the ability to use gdate style syntax to format the detail files and table names. I have my system setup to use different tables for each month of each year {ie: acct_stop_2003aug,...}, and my implementation creates the tables if they don't exist.

I have also written a detail file parser but it is not GPL, my last implementation before integrating its functionality into cistron supported a runtime configurable attribute map, but I don't remember if it created tables on the fly. I might be able to send you a binary of my parser but I can't send the source without a licence.

We keep the all the detail files and dumps of the all db tables on cdrom's for dispute purposes. The only problem with my cistron system is there is a memory leak somewhere in the cistron code. Today there was a thread in this list implying that PAM has a leak, since I have been using PAM that may solve my leak problem if I disable it.

We are moving to freeradius, because it has native support for SQL authentication and accounting and is not custom software. I will be immersing myself into the PostgreSQL code to make sure it is robust enough to maintain the connection to the database and generate tables on the fly as required. I will also be wanting to make an attribute rewriting module to make weird {Ascend} nas servers attributes match common attributes using a configuration file {attribute-map.conf :)}. From my initial look their was a lot of work to be done, but in the latest code a lot of progress has been made.

I hope your problem does not indicate a serious problem.

Guy

Alan DeKok wrote:

"Jeff Sullivan" <[EMAIL PROTECTED]> wrote:


Now the load is 0.00 0.00 0.00 with accounting
still going to detail. Normal load with all going to postgres
was about 0.18. What can I do to prevent this from happening again?
I would like to go back to all postgres.



 My suggestion is to *always* log everything to the 'detail' file,
and post-process it to copy the data to postgresql.

That will give you better control over bad situations.

Alan DeKok.

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html





--
Guy Fraser
Network Administrator
The Internet Centre
780-450-6787 , 1-888-450-6787

There is a fine line between genius and lunacy, fear not, walk the
line with pride. Not all things will end up as you wanted, but you
will certainly discover things the meek and timid will miss out on.





- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to