You will get an "Out of Memory" error, since you have run out of V=V memory to allocate ...
Depending on the vagaries of the OS, all sorts of other hell may break loose as well, if your "process" out-of-memory condition corresponds to a general OS out-of-memory condition. That is to say that if your process has consumed all V=V memory in the system and there is no V=V memory left for allocation by *ANY* process or the OS itself, then AHWBL. (All Hell Will Break Loose). This is more typical of OS's of ill-conceived design (such as those from Microsoft). OSes that are of well conceived design (basically everything else) generally do not suffer the same ill effects. If only the "process" has hit its quota or V=V allocation limit, then only that process will be notified of the failure when it tries to allocate more memory, and the OS itself and other processes will be unafected since (presumably) there is still V=V memory available in the system -- you are just not allowed to have at it. --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of x >Sent: Friday, 15 December, 2017 09:31 >To: sqlite-users@mailinglists.sqlite.org >Subject: [sqlite] What happens if an in memory database runs out of >memory > >Suppose I execute “attach :memory: as mem” and then create a table in >mem that requires more space than the available RAM can hold what >will happen? >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
