Re: todo: plpgsql - tool to track code coverage - Mailing list pgsql-hackers

From Cédric Villemain
Subject Re: todo: plpgsql - tool to track code coverage
Date
Msg-id AANLkTin_AO1Hb6TpUqXc+8PVndsBHy0XhZGiGfWBjtQk@mail.gmail.com
Whole thread Raw
In response to todo: plpgsql - tool to track code coverage  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
2010/11/5 Pavel Stehule <pavel.stehule@gmail.com>:
> 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.

Yes, this is interesting.

--
Cédric Villemain               2ndQuadrant
http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: ALTER TABLE ... IF EXISTS feature?
Next
From: Dimitri Fontaine
Date:
Subject: Re: ALTER OBJECT any_name SET SCHEMA name