Consider the following information about a university database: • professors have an ssn, a name, an age, a rank, and a research specialty.• projects have a project number, a sponsor name , a starting date, an ending date, and a budget.• graduate students have an ssn, a name, an age, and a degree program (e. g., m. s.or ph.• each project is managed by one professor (known as the project’s principal investigator).• each project is worked on by one or more professors (known as the project’s co-investigators).• professors can manage and/or work on multiple projects.• each project is worked on by one or more graduate students (known as the project’s research assistants).• when graduate students work on a project, a professor must supervise their work on the project. graduate students can work on multiple projects, in which case they will have a (potentially different) supervisor for each one.• departments have a department number, a department name, and a main office.• departments have a professor (known as the chairman) who runs the department.• professor’s work in one or more departments and for each department that they work in, a time percentage is associated with their job.• graduate students have one major department in which they are working on their degree.• each graduate student has another, more senior graduate student (known as a student advisor) who advises him or her on what courses to take.3. (20pt) triggers and stored procedures: add the following triggers and stored procedures to your database: a. female_faculty(): a function that returns the percentage of the female faculty in the university. b. total_people(pno): a function that returns the total number of people (pi, co-pi, students) who work on the project with pno. c. faculty_restrict: a trigger to ensure that each project has at most 4 faculty members as co-pi. d. student_restrict: a trigger to ensure that a student works on no more than two projects. write in the postgresql