[Plproxy-users] plproxy 2.0.3rc1 is ready for testing

Marko Kreen markokr at gmail.com
Mon Nov 19 12:31:26 UTC 2007


I put the test release for 2.0.3 up:

 http://plproxy.projects.postgresql.org/testing/plproxy-2.0.3rc1.tar.gz

Big change is the result column handling.  It should not affect
anyone careful, but it would be still good to test it..

Also the scanner rework is dangerous, trying to affect flex
behaviour is major voodoo, there is some chance of crashes/memleaks
although everything seems fine thus far.

So please test.

Before final release I hope to convert docs to asciidoc, do
some cleanup and merge Steve's contibution.


I'm no good at release ETA's so lets say after week or two.

-- 
marko


Release notes follow:

  = Features =

    * Explicitly specify result column names and types in query.

      Lets say there is function somefunc(out id int4, out data text).
      Previously pl/proxy issued following query:

        SELECT * FROM somefunc()

      And later tried to work out which column goes where.  Now it issues:

        SELECT id::int4, data::text FROM somefunc()

      For functions without named return paramenters, eg. just "RETURNS text":

        SELECT r::text FROM anotherfunc() r

      This gives better type safety when using binary I/O, allows signatures
      differ in deterministic ways and creates safe upgrade path for signatures.

      Only downside is that existing functions with wildly different signatures
      stop working, but as they work on pure luck anyway, I'm not worried.

    * Quote function and result column names properly.

    * Set client_encoding on remote database to be equal to local one.

  = Fixes =

    * Support 8.3 (handle short varlena header)

    * Support old flex (2.5.4)  Previously flex >= 2.5.33 was required.

    * Fix 'make deb', include actual debian/changelog.

    * Remove config paramenter 'statement_timeout'.

      It was ignored previously and it cannot be made work in live env
      when working thru pgbouncer, so its better to drop it completely.
      The setting can be always set via normal ways.


More information about the Plproxy-users mailing list