todo: plpgsql - tool to track code coverage

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: todo: plpgsql - tool to track code coverage
Date: 2010-11-05 07:25:46
Message-ID: AANLkTinaLjvmyR42kQbEurw0=W7ZR+=6zXei9agk+p40@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

I am looking on http://kputnam.github.com/piggly/ site. I am thinking,
so can be very easy write low level support to plpgsql. And this can
to solve a some issue of plpgsql with lazy SQL full checking.

A raising syntax error of some SQL inside plpgsql after a months of
production usage is still problem. This or similar tool can minimalize
risks.

Regards

Pavel Stehule

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Itagaki Takahiro 2010-11-05 07:27:49 Re: SQL/MED estimated time of arrival?
Previous Message Jan Urbański 2010-11-05 07:19:07 Re: why does plperl cache functions using just a bool for is_trigger