Re: Good way to insert/update when you're not sure of duplicates?

From: Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>
To: 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 duplicates?
Date: 2003-09-26 15:44:27
Message-ID: 200309262114.27094.shridhar_daithankar@persistent.co.in
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

Shridhar

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Meskes 2003-09-26 16:00:59 Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Previous Message Dennis Gearon 2003-09-26 15:18:28 Re: Good way to insert/update when you're not sure of duplicates?