Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2007-02-09 Thread Pavel Stehule
OK, where are we on this patch? without changes. This task have to do anybody who better know PostgreSQL cache system than me. Regards Pavel --- Pavel Stehule wrote: Pavel Stehule [EMAIL PROTECTED] writes:

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2007-02-09 Thread Alvaro Herrera
Pavel Stehule wrote: OK, where are we on this patch? without changes. This task have to do anybody who better know PostgreSQL cache system than me. How about you submit a version without any caching, but which works correctly; and we worry about optimizations later?

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2007-02-09 Thread Pavel Stehule
Pavel Stehule wrote: OK, where are we on this patch? without changes. This task have to do anybody who better know PostgreSQL cache system than me. How about you submit a version without any caching, but which works correctly; and we worry about optimizations later? I can update and send

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2007-02-08 Thread Bruce Momjian
OK, where are we on this patch? --- Pavel Stehule wrote: Pavel Stehule [EMAIL PROTECTED] writes: This patch doesn't seem to cope with cases where the supplied tuple has the wrong number of columns, and it

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2006-09-15 Thread Pavel Stehule
Pavel Stehule [EMAIL PROTECTED] writes: This patch allows using any row expression in return statement and does transformation from untyped row to composite types if it's necessary. This patch doesn't seem to cope with cases where the supplied tuple has the wrong number of columns, and it

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2006-09-15 Thread Tom Lane
Pavel Stehule [EMAIL PROTECTED] writes: This patch doesn't seem to cope with cases where the supplied tuple has the wrong number of columns, and it doesn't look like it's being careful about dropped columns either. Also, that's a mighty bizarre-looking choice of cache memory context in

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2006-09-15 Thread Pavel Stehule
Pavel Stehule [EMAIL PROTECTED] writes: This patch doesn't seem to cope with cases where the supplied tuple has the wrong number of columns, and it doesn't look like it's being careful about dropped columns either. Also, that's a mighty bizarre-looking choice of cache memory context in

Re: [HACKERS] [PATCHES] plpgsql, return can contains any expression

2006-09-04 Thread Tom Lane
Pavel Stehule [EMAIL PROTECTED] writes: This patch allows using any row expression in return statement and does transformation from untyped row to composite types if it's necessary. This patch doesn't seem to cope with cases where the supplied tuple has the wrong number of columns, and it