using NOLOCK cause Cartesian joins - Mailing list pgsql-general

From Roger Gordon
Subject using NOLOCK cause Cartesian joins
Date
Msg-id 2C945D8B26BD434DA41931432B2397301460E9@piranha.emojodom01.emojo.com
Whole thread Raw
Responses Re: using NOLOCK cause Cartesian joins
Re: using NOLOCK cause Cartesian joins
List pgsql-general

Hi,

 

When we use WITH (NOLOCK) at the end of table list in a SELECT query, a Cartesian join is returned (i.e. approximately  6,500 records instead of 57, which is distressing. 

 

We are building a database-agnostic system; while I believe PostgreSQL is using a multiversion locking model and does not need WITH (NOLOCK), our application also must run against MS SQL Server and that uses a concurrency control locking model.  We are using PostgreSQL 7.3.2 on RedHat 7.2.

 

Any suggestions?

 

Thanks in advance,

Roger

**********************************************************************************

Privileged or Confidential Information may be contained within this message.
If you have received this message in error, you are kindly requested to destroy
it immediately and inform the sender by return. You are prohibited from using
or forwarding the contents in any way whatsoever.
Opinions carried within this message that run contrary to the official business
of Emojo are solely the individual opinions of the sender, and are not sanctioned
or endorsed by the company.

**********************************************************************************

#################################################################
This e-mail message has been scanned for Viruses and Content 
and cleared by Trend Micro InterScan
#################################################################

pgsql-general by date:

Previous
From: Hans-Jürgen Schönig
Date:
Subject: Re: [HACKERS] Proposal for a cascaded master-slave replication system
Next
From: Christopher Browne
Date:
Subject: Re: Proposal for a cascaded master-slave replication system