Re: Parallel Insert and Delete operation - Mailing list pgsql-general

From Albe Laurenz
Subject Re: Parallel Insert and Delete operation
Date
Msg-id D960CB61B694CF459DCFB4B0128514C208A4E32A@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Parallel Insert and Delete operation  ("Yelai, Ramkumar IN BLR STS" <ramkumar.yelai@siemens.com>)
Responses Re: Parallel Insert and Delete operation  (Moshe Jacobson <moshe@neadwerx.com>)
List pgsql-general
Yelai, Ramkumar IN BLR STS worte:
> Sent: Wednesday, October 31, 2012 12:40 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Parallel Insert and Delete operation
>
> Hi All,
>
> Please clarify me the following example.
>
> I have 2 tables
>
> Table1  - ( it has one primary key and few  columns )
> Table2  - ( it has one primary key and few columns.  It has one
foreign key, which refers table1
> primary key ).
>
> I have 2 operations, which are written in pl/pgsql procedure.
>
> Operation1() - Inserts the records to table2 at every hour basis.
> Operation2() - Delete the records from Table 1 and Table2 based on the
primary key.
>
> What if both operations are running at the time for the same primary
key.
>
> what I have to take care to run these two operations perfectly without
creating inconsistency in
> database.

With the foreign key in place there can be no entry in table2
that does not have a corresponding entry in table1.

Concurrency is solved with locks, so one of the concurrent
operations might have to wait until the other one is done.

That is handled by the database system automatically.

Yours,
Laurenz Albe


pgsql-general by date:

Previous
From: telenieko@gmail.com
Date:
Subject: Re: Average Balance "life"
Next
From: ChoonSoo Park
Date:
Subject: Re: How to setup chained CA?