Ramkumar Yelai wrote:
[is worried that a database might become inconsistent if conflicting INSERTs
and DELETEs occur]
> @Albe - I got you first point. The second point is little skeptical
because postgres could have been
> avoided this lock by using MVCC. Please correct me if I am wrong?
Which
Ramkumar Yelai wrote:
[is worried that a database might become inconsistent if conflicting
INSERTs and DELETEs occur]
> @Albe - I got you first point. The second point is little skeptical
because postgres could have been
> avoided this lock by using MVCC. Please correct me if I am wrong?
Which l
te:
> Sent: Wednesday, October 31, 2012 12:40 PM
> To: pgsql-general@postgresql.org<mailto:pgsql-general@postgresql.org>
> Subject: [GENERAL] Parallel Insert and Delete operation
>
> Hi All,
>
> Please clarify me the following example.
>
> I have 2 tables
>
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
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
>
> Table
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.
