> -Original Message-
> From: Jim Nasby [mailto:jim.na...@bluetreble.com]
> Sent: Wednesday, June 01, 2016 11:32 PM
> To: Kaigai Kouhei(海外 浩平); Gavin Flower; Joe Conway; Ants Aasma; Simon Riggs
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Does people favor t
On 5/30/16 9:05 PM, Kouhei Kaigai wrote:
Due to performance reason, location of each element must be deterministic
without walking on the data structure. This approach guarantees we can
reach individual element with 2 steps.
Agreed.
On various other points...
Yes, please keep the discussion h
> -Original Message-
> From: Gavin Flower [mailto:gavinflo...@archidevsys.co.nz]
> Sent: Tuesday, May 31, 2016 9:47 AM
> To: Kaigai Kouhei(海外 浩平); Joe Conway; Jim Nasby; Ants Aasma; Simon Riggs
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Does people fa
On 31/05/16 12:01, Kouhei Kaigai wrote:
On 05/29/2016 04:55 PM, Kouhei Kaigai wrote:
For the closer integration, it may be valuable if PL/R and PL/CUDA can exchange
the data structure with no serialization/de-serialization when PL/R code tries
to call SQL functions.
I had been thinking about so
> On 05/29/2016 04:55 PM, Kouhei Kaigai wrote:
> > For the closer integration, it may be valuable if PL/R and PL/CUDA can
> > exchange
> > the data structure with no serialization/de-serialization when PL/R code
> > tries
> > to call SQL functions.
>
> I had been thinking about something similar
On 05/29/2016 04:55 PM, Kouhei Kaigai wrote:
> For the closer integration, it may be valuable if PL/R and PL/CUDA can
> exchange
> the data structure with no serialization/de-serialization when PL/R code tries
> to call SQL functions.
I had been thinking about something similar. Maybe PL/R can cr
c: pgsql-hackers@postgresql.org
> >> Subject: Re: [HACKERS] Does people favor to have matrix data type?
> >>
> >> On 05/28/2016 07:12 AM, Kouhei Kaigai wrote:
> >>> Sparse matrix! It is a disadvantaged area for the current array format.
> >>>
> >>
; Subject: Re: [HACKERS] Does people favor to have matrix data type?
>>
>> On 05/28/2016 07:12 AM, Kouhei Kaigai wrote:
>>> Sparse matrix! It is a disadvantaged area for the current array format.
>>>
>>> I have two ideas. HPC folks often split a large mat
> -Original Message-
> From: Joe Conway [mailto:m...@joeconway.com]
> Sent: Sunday, May 29, 2016 1:40 AM
> To: Kaigai Kouhei(海外 浩平); Jim Nasby; Ants Aasma; Simon Riggs
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Does people favor to have matrix data type?
On 05/28/2016 07:12 AM, Kouhei Kaigai wrote:
> Sparse matrix! It is a disadvantaged area for the current array format.
>
> I have two ideas. HPC folks often split a large matrix into multiple
> grid. A grid is typically up to 1024x1024 matrix, for example.
> If a grid is consists of all zero eleme
> On 5/25/16 7:46 AM, Kouhei Kaigai wrote:
> > My only concern is that domain type is not allowed to define type cast.
> > If we could add type cast on domain, we can define type transformation from
> > other array type to matrix.
>
> I've actually wished for that in the past, as well as casting t
On 5/25/16 7:46 AM, Kouhei Kaigai wrote:
My only concern is that domain type is not allowed to define type cast.
If we could add type cast on domain, we can define type transformation from
other array type to matrix.
I've actually wished for that in the past, as well as casting to
compound typ
Kouhei Kaigai writes:
> The 'matrix' data type as domain type of real[] is an option to implement.
> We can define operators on the domain types, thus, it allows us to process
> large amount of calculation by one operation, in native binary speed.
Don't go that way, it will cause you nothing but
; Subject: Re: [HACKERS] Does people favor to have matrix data type?
> >
> > On 25 May 2016 at 03:52, Kouhei Kaigai wrote:
> >
> >
> > In a few days, I'm working for a data type that represents matrix in
> > mathematical area. Does people favor to hav
> On Wed, May 25, 2016 at 10:38 AM, Simon Riggs wrote:
> > On 25 May 2016 at 03:52, Kouhei Kaigai wrote:
> >>
> >> In a few days, I'm working for a data type that represents matrix in
> >> mathematical area. Does people favor to have this data type in the core,
> >> not only my extension?
> >
> >
> -Original Message-
> From: Simon Riggs [mailto:si...@2ndquadrant.com]
> Sent: Wednesday, May 25, 2016 4:39 PM
> To: Kaigai Kouhei(海外 浩平)
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Does people favor to have matrix data type?
>
> On 25 May 2016
On Wed, May 25, 2016 at 10:38 AM, Simon Riggs wrote:
> On 25 May 2016 at 03:52, Kouhei Kaigai wrote:
>>
>> In a few days, I'm working for a data type that represents matrix in
>> mathematical area. Does people favor to have this data type in the core,
>> not only my extension?
>
>
> If we underst
On 25 May 2016 at 03:52, Kouhei Kaigai wrote:
> In a few days, I'm working for a data type that represents matrix in
> mathematical area. Does people favor to have this data type in the core,
> not only my extension?
>
If we understood the use case, it might help understand whether to include
it
Hi
2016-05-25 4:52 GMT+02:00 Kouhei Kaigai :
> In a few days, I'm working for a data type that represents matrix in
> mathematical area. Does people favor to have this data type in the core,
> not only my extension?
>
> Like oidvector or int2vector, it is one of array type with a few
> restrictio
In a few days, I'm working for a data type that represents matrix in
mathematical area. Does people favor to have this data type in the core,
not only my extension?
Like oidvector or int2vector, it is one of array type with a few
restrictions:
- 2 dimensional only
- never contains NULL
- elemen
20 matches
Mail list logo
