| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | wang chaoyong <wcy(dot)sei(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, mqzhou(at)sei(dot)ecnu(dot)edu(dot)cn |
| Subject: | Re: How to hack the storage component？ |
| Date: | 2013-01-18 09:26:50 |
| Message-ID: | 50F9155A.90501@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.01.2013 11:02, wang chaoyong wrote:
> Hi folks,
>
> Currently, I'm trying to read the storage component, since it's biased
> towards the lower layer, seems more difficult to understand and debug. All
> the materials I have found are the original papers on
> http://db.cs.berkeley.edu, I'm wondering how much it have been changed
> since Postgres. Could you please give me some suggestions? Thanks.
It has changed a lot since the Berkeley times. I doubt the original
papers are of much use anymore in understanding modern PostgreSQL.
You'll want to read src/backend/storage/smgr/README, although there
isn't much there. Also make sure you read the "Database Physical
Storage" section in the user manual,
http://www.postgresql.org/docs/devel/static/storage.html.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2013-01-18 09:47:00 | Re: Starting Postgres : user from same group |
| Previous Message | Heikki Linnakangas | 2013-01-18 09:20:57 | Re: Re: Slave enters in recovery and promotes when WAL stream with master is cut + delay master/slave |