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
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?
> >---
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]> wr
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 colu
"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
"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 contex
"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 i
"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
I am going to need this in 24 hours or it might not make it into 8.2.
---
bruce wrote:
>
> While this patch has new regression tests, it doesn't have new expected
> output for it. Please update the patch to supply that.
Hello
I am sending corrected version.
regards
Pavel Stehule
While this patch has new regression tests, it doesn't have new expected
output for it. Please update the patch to supply that. Thanks.
---
Pavel Stehule wr
While this patch has new regression tests, it doesn't have new expected
output for it. Please update the patch to supply that. Thanks.
---
Pavel Stehule wrote:
> Hello
>
> This patch allows using any row expression in re
Hello
This patch allows using any row expression in return statement and does
transformation from untyped row to composite types if it's necessary.
Regards
Pavel Stehule
_
Chcete sdilet sve obrazky a hudbu s prateli? http://messe
Hello,
this patch allow any expression in return statement and it does simply
casting from non type record into typed records. Allows same casting as
assign statement.
Regards
Pavel Stehule
From: Bruce Momjian <[EMAIL PROTECTED]>
To: Pavel Stehule <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED],
13 matches
Mail list logo
