Re: Inspection of row types in pl/pgsql and pl/sql

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inspection of row types in pl/pgsql and pl/sql
Date: 2009-11-14 17:21:24
Message-ID: 162867790911140921j50227d19r475bf00d6fb67d4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/11/14 Andrew Dunstan <andrew(at)dunslane(dot)net>:
>
>
> Pavel Stehule wrote:
>>
>> Hello
>>
>> new hstore has a very nice interface for record field iteration
>>
>>
>
> Yes, and I have used it, but it really would be nicer to have some
> introspection facilities built in, especially for use in triggers.

I am not sure. PL/pgSQL is really bad language for this task. Any
procedure developed in plpgsql should be pretty slow. Personally I am
happy with current 8.5. If some need it, the he could to use hstore -
contrib modules are not problem on every platform, but cannot generate
too much general triggers simply (what is good). I understand well to
motivation. But now I thinking, so general triggers are very bad and
risk technique and is better do things else. If someone really need
it, then he could to write C procedure.

Regards
Pavel Stehule

>
> cheers
>
> andrew
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2009-11-14 17:26:13 Writeable CTE patch
Previous Message Magnus Hagander 2009-11-14 17:12:33 Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"