| From: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: knngist - 0.8 |
| Date: | 2010-10-16 22:13:30 |
| Message-ID: | AANLkTimcJ9SdKiXwd-J69DyGvDNOSMyxukJ-Ui8j6Zrm@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 16, 2010 at 10:17 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On lör, 2010-10-16 at 09:23 -0700, Paul Ramsey wrote:
>> >> (And, if we are going to break everything
>> > in sight, now would be a good time to think about changing typmod to
>> > something more flexible than one int32.)
>>
>> As someone who is jamming geometry type, spatial reference number and
>> dimensionality into said 32bit typmod, let me say emphatically ...
>> Amen!
>
> So what kind of data structure would you like for a typmod?
I'm a primitive enough beast that just having 64-bits would make me
happy. As a general matter though, a bytea?
P
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-16 22:52:27 | Re: Extensions, this time with a patch |
| Previous Message | Hitoshi Harada | 2010-10-16 20:18:03 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |