Hi,

On Mon, 29 Jul 2013, László Böszörményi (GCS) wrote:
> On Fri, Jul 26, 2013 at 11:13 AM, Raphaël Hertzog <hert...@debian.org> wrote:
> > http://www.sqlite.org/limits.html#max_variable_number
> >
> > Upstream document this compile-time limit. But 999 is ridiculously low
> > by today's standard of memory size. This limit can be increased to
> > something bigger.
> [...]
> > In my use case, I have queries that embed all the Debian package names so
> > I need several dozens of thousands of variables. This is for a query that
> > Django generates and it's similar to something like this:
> > SELECT * FROM packageinfos WHERE name in (?,?,?,…).
>  What would be an acceptable value for your use case? I don't want to
> just shot a number, but choose one that sounds reasonable.

Given that we are at 40000 unique binary package names and that we want to
accomodate for some future growth, 100000 would be enough for a while for
me.

But you might want to estimate "reasonable" based on the memory that those
arguments consumes and the average amount of memory that you get on modern
machines.

I bet that you will get a bigger number and that Apple's choice of 500000
is not unreasonable.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to