Postgres Pro
Downloads
Home   >   mailing lists

Re: Good way to insert/update when you're not sure of duplicates? - Mailing list pgsql-general

From Shridhar Daithankar
Subject Re: Good way to insert/update when you're not sure of duplicates?
Date
Msg-id 200309262114.27094.shridhar_daithankar@persistent.co.in
Whole thread Raw
In response to Good way to insert/update when you're not sure of duplicates?  (Curtis Stanford <curtis@stanfordcomputing.com>)
Responses Re: Good way to insert/update when you're not sure of duplicates?  (Dennis Gearon <gearond@fireserve.net>)
Re: Good way to insert/update when you're not sure of  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-general
Tree view 
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

pgsql-general by date:

Previous
From: Shridhar Daithankar
Date:
Subject: Re: Good way to insert/update when you're not sure of duplicates?
Next
From: Dennis Gearon
Date:
Subject: Re: Good way to insert/update when you're not sure of duplicates?