Re: Need help to identify stray row in a table

From: சிவகுமார் மா <masivakumar(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Need help to identify stray row in a table
Date: 2010-04-24 01:54:58
Message-ID: y2m139e14f01004231854y98c87404y343f6c2ef3063d7e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2010/4/23 Merlin Moncure <mmoncure(at)gmail(dot)com>:
>
> There's way too much logic going on there for me to test all the
> different cases.
>
> I suspect this is your problem: you triggered a case somehow which is
> not handled properly via your labyrinth of switches and loops.  I
> highly doubt this is a case of database corruption.  My advice here
> would be to not rely on procedural code to guard against something
> which can and should be enforced by a constraint.   If something is
> wrong (source_id being null), declare it to be wrong -- that way the
> next time this happens the constraint will bounce the transaction and
> you can catch the problem when it happens as opposed to reverse
> engineering it.
>
Thanks for the suggestion and help. Will work on changing the function
and constraints for enforcing data accuracy.

Thanks and regards,

Ma Sivakumar

மா சிவகுமார்
எல்லோரும் எல்லாமும் பெற வேண்டும்
http://masivakumar.blogspot.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sunpeng 2010-04-24 03:04:23 how to set CACHEDEBUG ?
Previous Message Ben Chobot 2010-04-24 01:06:39 Re: how to invalidate a stored procedure's plan?