Postgres PL SQL bug? - Mailing list pgsql-general

From Shaun Clements
Subject Postgres PL SQL bug?
Date
Msg-id 100F78F2B203444BB161BBA7077FF6131CD9CC@srldbexc003.relyant.co.za
Whole thread Raw
Responses Re: Postgres PL SQL bug?  (Richard Huxton <dev@archonet.com>)
List pgsql-general
Hi All
 
Im hoping someone has an answer for this mystery.
I have a stored procedure, which queries a table, of about 400-000 records, into a RECORD, ordered by three columns.
I am using a conditional INSERT, UPDATE command, based on evaluating the last record.column, against the new record.column, to ascertain whether it requires, an UPDATE or INSERT.
 
The problem is the records are not ORDERED properly into the RECORD, and when looping through it,it is trying to INSERT somewhere down the line, and is returning an error, saying it cant INSERT a duplicate key into unique.. etc.
 
Any suggestions, the postgres version is 7.3
 
Thanks in advance.
 
A {FONT-FAMILY: verdana; TEXT-DECORATION: none } A:active {COLOR: #ff0000; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:link {COLOR: #003366; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:visited {COLOR: #003366; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:hover {COLOR: #ff0000; FONT-FAMILY: verdana; TEXT-DECORATION: underline } .small_text {FONT-SIZE: 9px; COLOR: #003366; FONT-FAMILY: verdana } Kind Regards,
Shaun Clements

pgsql-general by date:

Previous
From: "Qingqing Zhou"
Date:
Subject: Re: Postgres Processing Help !!!!
Next
From: Greg Stark
Date:
Subject: Re: Debugging deadlocks