tgl wrote: > strk <[EMAIL PROTECTED]> writes: > > If I run that again, *exactly the same query*: > > PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND > > 566 pgsql 14 0 126M 126M 3396 S 0.0 16.8 7:13 postmaster > > > It looks like someone is leaking memory, either postgres, postgis or geos. > > On some platforms top's report of memory used can be misleading, because > it begins to count each page of shared memory against a process when the > process first touches that page. So if you have a big scan that touches > more and more of the shared buffers, the reported process size goes up > --- but there's really no memory leak. Try a plain "select count(*)" > against your table and see if you see the same change in reported size.
No changes in size with count(*). Testing platform is FreeBSD. > Alternatively, if the reported size continues to increase well beyond > your shared memory allocation, then I'd believe that as evidence of a > leak. > > regards, tom lane thanks for you answer. --strk; ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
