| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
| Cc: | Dennis Gearon <gearond(at)fireserve(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Good way to insert/update when you're not sure of |
| Date: | 2003-09-26 16:02:54 |
| Message-ID: | Pine.LNX.4.33.0309261002100.21251-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 26 Sep 2003, Shridhar Daithankar wrote:
> On Friday 26 September 2003 21:08, Dennis Gearon wrote:
> > corruption of the databases, if I'm correct.
>
> > Shridhar Daithankar wrote:
> > >On Friday 26 September 2003 20:48, Dennis Gearon wrote:
> > >>I didn't think mulitple backends worked.
> > >
> > >Why? Why can't you insert using multiple backends? I mean is there a
> > > problem?
>
> How does database gets corrupted? If you have 20 backend inserting their own
> chunk of data in separate transactions, where does database corruption comes
> in picture?
>
> That's the whole idea of transactions.
I think Dennis is confusing multiple backends (legal and safe, each
connection gets its own backend) with multiple postmasters (not legal,
very unsafe, causes corruption, etc...)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2003-09-26 16:11:08 | Re: Good way to insert/update when you're not sure of duplicates? |
| Previous Message | Michael Meskes | 2003-09-26 16:00:59 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |