| 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-16 15:19:28 |
| Message-ID: | FE874572-69D2-492C-BB3A-DDBE0F2D9DEF@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Sep 16, 2017, at 8:23 AM, Rafal Pietrak <rafal(at)ztk-rp(dot)eu> wrote:
>
>
>
> W dniu 16.09.2017 o 15:45, Adam Brusselback pisze:
>> Here is the last discussion I saw on
>> it: https://www.postgresql.org/message-id/flat/90261791-b731-a516-ab2a-dafb97df4464%40postgrespro(dot)ru#90261791-b731-a516-ab2a-dafb97df4464(at)postgrespro(dot)ru
>> <https://www.postgresql.org/message-id/flat/90261791-b731-a516-ab2a-dafb97df4464%40postgrespro(dot)ru#90261791-b731-a516-ab2a-dafb97df4464(at)postgrespro(dot)ru>
>>
>
> I can see the discussion is packed with implementation details. That's
> promising :)
>
> Thenx!
>
>
For those of us scoring at home, here's what I have:
1 You have a 6-deep hierarchy over 17 document types
you concede that standard master-detail/inheritance accomplishes what you need w.r.t to documents
2 You don't have enough document instances to warrant partitioning
3 Your remaining problem is your workflow
4 You have an academic interest in multi-table indexing
Does this sum up the situation?
Have you shared your current schema?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafal Pietrak | 2017-09-16 17:18:54 | Re: looking for a globally unique row ID |
| Previous Message | Rafal Pietrak | 2017-09-16 14:23:09 | Re: looking for a globally unique row ID |