Peter Eisentraut writes:
> There might be a different bug here. This doesn't look right:
The UPDATE lacks a WHERE clause :-(
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgre
On ons, 2009-11-11 at 19:45 -0500, Tom Lane wrote:
> > try
> > insert
> > catch unique_constraint_violation
> > update
> > end try
>
> > this will end up cluttering the logs with all the constraint violation
> > messages.
>
> Really? It's not supposed to.
There might be a different bug
Peter Eisentraut writes:
> Is it at all reasonable to try to create some mechanism so that
> exceptions (elog) that are caught and not rethrown do not end up in the
> log? For example, when you write code that does something like
> try
> insert
> catch unique_constraint_violation
> updat
Is it at all reasonable to try to create some mechanism so that
exceptions (elog) that are caught and not rethrown do not end up in the
log? For example, when you write code that does something like
try
insert
catch unique_constraint_violation
update
end try
this will end up cluttering t
