[pgpointcloud] Toast(ed)

[Paul Ramsey]

> Since we store patches with practically no extra information next to them in the tuple, just reading the PC_MemSize (I think that’s the function) of the patch gives an idea of storage you can use to bump up your patch size to close to the maximum (8kb). 

Is there a way we could communicate from the db to drivers.pgpointcloud.writer an automatic toast'able patch size based on this info? 
Yes, no, maybe so. You already have the core info (before looking at data) in your pipeline. The schema gives you an implicit point size. All you don’t know is the compression ratio, and until you start compressing actual data you don’t know that.

> You can also recompile your database with a higher page size if you’re feeling hacky. 

Is there any possibility that pg could be improved to allow tables of varying page sizes? I suppose increasing the page size generally across an entire database could cause some unforeseen pathologies. 
Next you’ll want to start f’ing with the gravitational constant. If you want to make the experiment, the page size is just a #define, and it might actually be a configure option even. It does cover the whole database though, variable page sizes aren’t on.

P.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgpointcloud/attachments/20140206/42ee7201/attachment.html>