On Tue, Nov 2, 2010 at 5:47 AM, RP Khare
wrote:
> I want to know how we can handle this issue in PostgreSQL.
>
When you load your 50,000 record batch, do it inside a transaction
block and "SELECT FOR UPDATE" the rows instead of plain "SELECT".
That will lock those rows from being updated by other
On 2 November 2010 10:47, RP Khare wrote:
> Hi,
>
> Though the following issue we are facing at present with Oracle 10g
> database, but I just want to know how PostgreSQL would solve this problem.
> We are planning a migration to any open-source RDBMS in future, so just
> wanted to clear this iss
Hi,
Though the following issue we are facing at present with Oracle 10g database,
but I just want to know how PostgreSQL would solve this problem. We are
planning a migration to any open-source RDBMS in future, so just wanted to
clear this issue.
Let me clear the scenario, the real-life issue
