| From: | Dennis Gearon <gearond(at)fireserve(dot)net> |
|---|---|
| To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Good way to insert/update when you're not sure of duplicates? |
| Date: | 2003-09-26 16:11:08 |
| Message-ID: | 3F74651C.9080103@fireserve.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Well, I may have my merms tixed up!
There is ONE component of Postgres that can only be accessing the
database by itself. Maybe it's not the 'backend', it's probably the
postmaster. Are they the same? I don't know.
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.
>
> Shridhar
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eugene Strulyov | 2003-09-26 16:48:53 | transaction timeout |
| Previous Message | scott.marlowe | 2003-09-26 16:02:54 | Re: Good way to insert/update when you're not sure of |