On Fri, Feb 27, 2009 at 10:37 AM, Heikki Linnakangas
wrote:
> But I wonder, why does plpgsql debugger even try to display those variables
> after the exception block? I'm not familiar with the tool; I'm guessing that
> it just displays all variables, regardless of scope.
I believe so. I'm not th
Dave Page wrote:
On Mon, Feb 2, 2009 at 8:46 PM, Tom Lane wrote:
"Robert Walker" writes:
I have a function that basically loops through a query and uses the results
from that query to do an individual insert into another table, and if there
is a unique violation, it simply raises a notice and
On Mon, Feb 2, 2009 at 8:46 PM, Tom Lane wrote:
> "Robert Walker" writes:
>> I have a function that basically loops through a query and uses the results
>> from that query to do an individual insert into another table, and if there
>> is a unique violation, it simply raises a notice and continues
On Mon, Feb 2, 2009 at 8:46 PM, Tom Lane wrote:
> "Robert Walker" writes:
>> I have a function that basically loops through a query and uses the results
>> from that query to do an individual insert into another table, and if there
>> is a unique violation, it simply raises a notice and continues
"Robert Walker" writes:
> I have a function that basically loops through a query and uses the results
> from that query to do an individual insert into another table, and if there
> is a unique violation, it simply raises a notice and continues on. When
> trying to debug the function within PgAdmi
The following bug has been logged online:
Bug reference: 4635
Logged by: Robert Walker
Email address: r.wal...@mtcworldwide.com
PostgreSQL version: 8.3.5
Operating system: WinXP SP2 32-bit
Description:postgres.exe crash when RAISE NOTICE during debugging of
PL/pgSQL f
