| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Hope Ho <ho(dot)hope(at)yahoo(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: modularity of PostgreSQL |
| Date: | 2008-01-17 23:14:46 |
| Message-ID: | 200801172314.m0HNEkU27830@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hope Ho wrote:
> Dear all,
>
> I have some questions about PostgreSQL's modularity. We know that
> PostgreSQL is famous for its good modularity, which allows users to
> select which part they need. It also allow developers to easily replace
> one part without affecting other parts. However, as I know, most
> database engine, like MySQL, has such modularity: layered architecture
> and small pieces of functionalities. Actually, it's a rule recognized
> by lots of software design. Why is only PostgreSQL entitled "good
> modularity"?
Because Postgres is modulare beyond the source code level. The modules
can be replaced without reprogramming the backend database, like
functions, triggers, operators, server-side languages, etc. And you can
even add new data types without having to modify the database backend
code.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-17 23:46:52 | Re: modularity of PostgreSQL |
| Previous Message | Tom Lane | 2008-01-17 23:10:16 | Re: [ADMIN] postgresql in FreeBSD jails: proposal |