meteor-pg icon indicating copy to clipboard operation
meteor-pg copied to clipboard
verified publisher icon numtel

Document limitations

Open dandv opened this issue 10 years ago • 3 comments

Considering using this; what are the current limitations? Would be nice to document them in the README.

dandv avatar May 09 '15 02:05 dandv

Note: This has now been fixed!

~~I would say that the memory usage is the biggest limitation. See this issue on the pg-live-select repo. As illustrated in the memory usage graphs for 380 and 400 rows, it seems there is a memory leak with long result sets. Try to keep result set lengths as short as possible.~~

~~As far as I can tell, it's an issue with the node-postgres package as the test that revealed that leak is only performing a query repeatedly, not actually running the entire live select process. More work is still required to be sure though.~~

numtel avatar May 10 '15 05:05 numtel

As of the just released version 1.0.0, the memory leak has been fixed by rewriting pg-live-select to use callbacks throughout instead of Promises provided by Babel.

numtel avatar May 12 '15 09:05 numtel

I'd rather not open a new thread to post this question, if that's okay (I can always delete this) - if I have an existing app and it's using Mongo/miniMongo, can I just do a meteor reset after installing numtel:pg, numtel:pg-server and setting up the connection string?

funkytaco avatar Jun 12 '15 03:06 funkytaco