From: | Gmail <robjsargent(at)gmail(dot)com> |
---|---|
To: | Rafal Pietrak <rafal(at)ztk-rp(dot)eu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: looking for a globally unique row ID |
Date: | 2017-09-18 00:34:27 |
Message-ID: | 68F355DF-49F9-49D5-A8B8-C8564D3143CC@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> As you may have noticed, I've put significant effort to focus the
> discussion on my actual question: the "global index" (which btw I didn't
> know is called this way here - if I new, I'd probably could have google
> it instead). This was intentional. I like my schema design very much and
> I'm unwilling to part with it.
>
>
> no, it doesn't.
>
> T1 is empty. It's just a head of inheritance tree.
>
> There is no guarantee (index on T1 will have no entries). But naturally
> there are ways to "smartly" partition the ID space allocated to
> subtables of T1.
>
>
OK. Wow, that's sure not how I read the docs on inheritance, but I've never used the construct thinking it was largely syntactic sugar on master/detail based scheme designs.
But since you're wed irrevocably to your scheme design, I'll bow out of this discussion.
All the best,
rjs
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-09-18 01:43:00 | Re: Selecting a daily puzzle record - which type of column to add? |
Previous Message | John R Pierce | 2017-09-17 20:59:47 | Re: advisory locks namespace? |