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:
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?
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
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
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
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
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
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