From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Florian Pflug <fgp(at)phlo(dot)org>, James William Pye <lists(at)jwp(dot)name>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Urbański <wulczer(at)wulczer(dot)org>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: hstores in pl/python |
Date: | 2010-12-15 19:21:35 |
Message-ID: | AANLkTi=Dpxy75C=p983LMFLy-0GHgEP50z8J4eAc-OPa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/12/15 Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
>
>
> 2010/12/15 Robert Haas <robertmhaas(at)gmail(dot)com>
>
> On Wed, Dec 15, 2010 at 2:14 PM, Robert Haas <robertmhaas(at)gmail(dot)com>
>> wrote:
>> > On Wed, Dec 15, 2010 at 1:22 PM, Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
>> wrote:
>> >> Yes, but range of PostgreSQL's OIDs can be reserved. One or even ten
>> >> millions, e.g. can be enough.
>> >
>> > No, they can't. PostgreSQL is already deployed without any such
>> > restriction. You can "reserve" those OIDs because they may already be
>> > in use on any given system.
>>
>> Err, you CAN'T reserve these OIDs because blah blah.
>>
> Right.
> Proposed identifiers wins in this case.
>
I mean Java-styled identifiers.
>
>> --
>>
>> Robert Haas
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
>
> --
> // Dmitriy.
>
>
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-12-15 19:22:51 | Re: Complier warnings on mingw gcc 4.5.0 |
Previous Message | Dmitriy Igrishin | 2010-12-15 19:20:49 | Re: hstores in pl/python |