| From: | TJ O'Donnell <tjo(at)acm(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: do separate databases have any impact each other? |
| Date: | 2005-08-16 14:11:14 |
| Message-ID: | 4301F402.70203@acm.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera wrote:
> On Mon, Aug 15, 2005 at 01:15:03PM -0700, TJ O'Donnell wrote:
>
>>While writing installation instructions for my new PostgreSQL product, I
>>found myself
>>writing the following sentence:
>>"For first time users, we recommend building the gnova database,
>>since it has no impact on other databases."
>
>
> A problem not mentioned already is that if your database contains a C
> function and it has a bug which results in a crash, your whole
> production database will go down. This may not be desirable.
Well I have the perfect solution for that.... <grin>
I just won't write any buggy code!
Seriously, this could be a problem, especially since there is
3rd party software involved, too. Guess I've opened myself up for some
serious testing procedures. That's a good thing.
Since I'm writing in C++ with a thin interface to C for pg,
I catch a lot of nasty situtations which used to crash my C programs.
TJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aly Dharshi | 2005-08-16 14:20:49 | Re: Postgresql Books: Which one ? |
| Previous Message | Andrew Dunstan | 2005-08-16 14:10:21 | Re: Testing of MVCC |