Committed the last version.
I updated the documentation which previously claimed that what you
implemented wasn't supported.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
2011/2/9 Jan Urbański :
> I hope this version does the right thing, while still avoiding the
> performance hit of looking up I/O funcs every time a row is returned.
> Actually, PL/Perl *does* look up the I/O funcs every time, so in the
> worst case I can just drop this optimisation. But let's hope
On 07/02/11 06:10, Hitoshi Harada wrote:
> 2011/2/7 Jan Urbański :
>> On 04/02/11 16:26, Hitoshi Harada wrote:
>>> 2011/1/28 Jan Urbański :
On 27/01/11 00:41, Jan Urbański wrote:
> I'm also attaching an updated version that should apply on top of my
> github refactor branch (or increme
2011/2/7 Jan Urbański :
> On 04/02/11 16:26, Hitoshi Harada wrote:
>> 2011/1/28 Jan Urbański :
>>> On 27/01/11 00:41, Jan Urbański wrote:
I'm also attaching an updated version that should apply on top of my
github refactor branch (or incrementally over the new set of refactor
patches
On 04/02/11 16:26, Hitoshi Harada wrote:
> 2011/1/28 Jan Urbański :
>> On 27/01/11 00:41, Jan Urbański wrote:
>>> I'm also attaching an updated version that should apply on top of my
>>> github refactor branch (or incrementally over the new set of refactor
>>> patches that I will post shortly to th
2011/1/28 Jan Urbański :
> On 27/01/11 00:41, Jan Urbański wrote:
>> I'm also attaching an updated version that should apply on top of my
>> github refactor branch (or incrementally over the new set of refactor
>> patches that I will post shortly to the refactor thread).
>
> Attached is a patch for
On 27/01/11 00:41, Jan Urbański wrote:
> I'm also attaching an updated version that should apply on top of my
> github refactor branch (or incrementally over the new set of refactor
> patches that I will post shortly to the refactor thread).
Attached is a patch for master, as the refactorings have
On 24/01/11 05:42, Hitoshi Harada wrote:
> 2011/1/23 Jan Urbański :
>> On 22/01/11 11:15, Hitoshi Harada wrote:
> I tested the new incremental patch and the previous example works
> fine. I don't know if this can be handled properly but another example
> is:
>
> regression=# create function func1(
2011/1/23 Jan Urbański :
> On 22/01/11 11:15, Hitoshi Harada wrote:
>> This is a review for
>> https://commitfest.postgresql.org/action/patch_view?id=460
>
> Thanks,
>
>> One issue is typmod of record type.
>>
>> regression=# create or replace function func1(t text) returns record
>> as $$ return
On 22/01/11 11:15, Hitoshi Harada wrote:
> This is a review for
> https://commitfest.postgresql.org/action/patch_view?id=460
Thanks,
> One issue is typmod of record type.
>
> regression=# create or replace function func1(t text) returns record
> as $$ return {'name': t, 'value': 0} $$ language
This is a review for https://commitfest.postgresql.org/action/patch_view?id=460
== Submission ==
The patch applies and compiles with success, on the top of the general
refactor patch. It is possible it cannot in HEAD now that the part of
the refactor patch applied in the core. I'll check it after
11 matches
Mail list logo
