Re: pg_proc.probin should become text?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_proc.probin should become text?
Date: 2009-08-04 14:46:36
Message-ID: 20090804144636.GC6494@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Stehule escribió:

> I agree, so information about patch would be store in text field. But
> I am not sure, if your fix isn't too simply. I haven't plan to compile
> plpgsql to C or to binary code. But could be interesting link postgres
> with some virtual machine like parrot or lua vm, and translate plpgsql
> to p code. It's maybe far future.

In this case I think it would make more sense to compile the code and
keep the p-code in backend local memory. Keeping compiled code around
in more permanent or global storage would only make sense if you had
large amounts of code, and in that case I think we'd want to have a more
concrete and complete proposal.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-04 14:48:12 Re: Alpha Releases: Docs?
Previous Message Tom Lane 2009-08-04 14:45:52 Re: Review: Revise parallel pg_restore's scheduling heuristic