Re: [HACKERS] CREATE SCHEMA IF NOT EXISTS

... 2) ALTER TABLE ... ADD [ COLUMN ] [ IF NOT EXISTS ] column_name ... 3) CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ IF NOT EXISTS ] [ name ] ON ... Regards, Volker -- Volker Grabsch ---<<(())>>--- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make change

[HACKERS] Missing optimization when filters are applied after window functions

ny work on this issue? Or am I wrong and this optimization should not be implemented for some reason? Regards, Volker -- Volker Grabsch ---<<(())>>--- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Missing optimization when filters are applied after window functions

Hitoshi Harada schrieb: > On Wed, May 16, 2012 at 12:50 AM, Volker Grabsch > wrote: > > I propose the following general optimization: If all window > > functions are partitioned by the same first field (here: id), > > then any filter on that field should be executed be

[HACKERS] Adding XSLT support to PostgreSQL core?

olished up and moved into core? Do you need some volunteer to put work into this? Even with the upcoming XQuery support, XSLT still has its place as a very useful templating language with lots of existing stylesheets in the wild. Greets, Volker -- Volker Grabsch ---<<(())>>--- --