TonyS <tony@xxxxxxxxxxxxxxxxxxx> writes: > Running "analyze verbose;" and watching top, the system starts out using no > swap data and about 4GB of cached memory and about 1GB of used memory. As it > runs, the amount of used RAM climbs, and eventually the used swap memory > increases to 100% and after being at that level for a couple of minutes, the > analyze function crashes and indicates "server closed the connection > unexpectedly." ANALYZE is supposed to work in a constrained amount of memory, though that amount depends quite a bit on what the data is and what you've got the statistics target set to. We've heard reports that there are memory leaks in (some versions of?) PostGIS's analyze support. Whether that would apply to you would depend on whether you're using PostGIS. Hard to say more without a lot more concrete info about what your data is, what PG version you're using, etc. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
