From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Yannick Lecaillez <yl(at)itioweb(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgresql on SAN |
Date: | 2004-07-07 12:53:27 |
Message-ID: | 200407071253.i67CrRb03164@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yannick Lecaillez wrote:
> Thanks a lot for all people which answer.
>
> I have this "clustering on SAN" problem today and i think it could be
> less harder to implement this today than it was for Oracle in 1993
> (since i can find a lot of work in opensource which could be interesting
> in this project : distributed lock, clustered shared memory, etc ...).
>
> I will try to have a look about all these things btw, i haven't got
> the pretention to suceed to do anything ... Just look and see
> a bit more deeply how it could be hard.
>
> Is there something like a "big picture" about postgres internal ?
> What path is used from the SQL query to the hard-disk files ? About
> the internal locking mechanism ? about the usage of the shared memory ?
> I see there is everything described in the postgres doc but no "big
> picture" which could help me to understand faster ... :(
Have you read the developers FAQ on the developers web page?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB SD | 2004-07-07 13:17:31 | Re: Point in Time Recovery |
Previous Message | spock | 2004-07-07 12:21:38 | Update pg_tables, pg_index views to show tablespace name? |