Re: Parallel Insert and Delete operation

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Yelai, Ramkumar IN BLR STS *EXTERN*" <ramkumar(dot)yelai(at)siemens(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Parallel Insert and Delete operation
Date: 2012-10-31 13:33:51
Message-ID: D960CB61B694CF459DCFB4B0128514C208A4E32A@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yelai, Ramkumar IN BLR STS worte:
> Sent: Wednesday, October 31, 2012 12:40 PM
> To: pgsql-general(at)postgresql(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jürgen Fuchsberger 2012-10-31 14:24:27 Corrupt Incrementally Updated Backup: missing pg_clog file
Previous Message Mahmoud Hakeem-Habeeb 2012-10-31 12:01:42 Delay streaming replication using a paramter