| 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:18:50 |
| Message-ID: | AANLkTi=9UuKtw=jti4EKrJgg_FbLYLJkZeNKCaOgQWq4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
// Dmitriy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2010-12-15 19:20:49 | Re: hstores in pl/python |
| Previous Message | Pavel Stehule | 2010-12-15 19:15:58 | Re: hstores in pl/python |