"Gevik Babakhani" <pgdev@xs4all.nl> writes:
> I am trying to catch and copy an error to be re-thrown later.
This is certainly not the right way to go about solving your problem.
If you need to refactor some of the column lookup routines to make
this patch work, then do so, but don't try to make an already-thrown
error not be an error. (One good reason for that is that you don't
really know what error you are catching --- it might be a report
of some low-level problem such as out-of-memory, for instance.)
The pattern you might want to follow is adding a noError boolean
parameter to functions you want to be able to get failure returns
back from.
regards, tom lane
