| From: | Chris Travers <chris(at)travelamericas(dot)com> |
|---|---|
| To: | Halford Dace <hal(at)stowe(dot)co(dot)za> |
| Cc: | Bhartendu Maheshwari <bhartendum(at)jataayusoft(dot)com>, Sam Barnett-Cormack <s(dot)barnett-cormack(at)lancaster(dot)ac(dot)uk>, PgSQL Admin List <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Running Postgres Daemons with same data files |
| Date: | 2003-12-09 13:14:00 |
| Message-ID: | 1070975639.977.7.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Case in point:
MS Access was designed to have multiple database managers manipulating
the files themselves directly and uses another file for locking
information. However-- as anyone who has ever worked with the process
will tell you: Don't do it. Data corruption (often unrecoverable) will
result.
The lessons we have learned from MS Access are:
1) Don't have 2 unrelated backends trying to access the same data and
2) Don't do it across a network.
IMO, this shows a fundamental design flaw in MS Access at least given
how it is marketed.
Don't try to do the same with PostgreSQL.
Best Wishes,
Chris Travers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2003-12-09 13:18:20 | Re: Full textsearch & gist (fwd) |
| Previous Message | Halford Dace | 2003-12-09 12:50:05 | Re: Running Postgres Daemons with same data files |