Re: [PERFORM] Storing large documents - one table or partition by doc?

2016-09-26 Thread Dev Nop
t mean lines must be renumbered on inserts/moves? On Mon, Sep 26, 2016 at 9:26 AM, Dev Nop wrote: > If GUIDs *stored in a binary format* were too large, then you won't be >> terribly happy with the 24 byte per-row overhead in Postgres. > > > Heh. In this case the ids have a li

Re: [PERFORM] Storing large documents - one table or partition by doc?

2016-09-24 Thread Dev Nop
Thank you Mike & Jim for your responses. > Are there other issues/requirements that are creating other performance concerns > that aren’t obvious in your initial post Yes, there are a few things: *1. Full document queries really are necessary* > it’s too much data to show on a web page, for ins

[PERFORM] Storing large documents - one table or partition by doc?

2016-09-23 Thread Dev Nop
I’m storing thousands of independent documents each containing around 20k rows. The larger the document, the more likely it is to be active with inserts and updates (1000s/day). The most common read query is to get all the rows for a single document (100s/day). It will be supporting real-time colla