randgen team mailing list archive

[Philip Stoev <philip@xxxxxxxxx>]

Fixed. The cut-off is at 10K records regardless of the size of the
records . For the default dataset, 100K records cause memory consumption
in excess of 1GB , so a 10K cut-off was chosen instead.

** Changed in: randgen
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Random
Query Generator Team, which is subscribed to Random Query Generator.
https://bugs.launchpad.net/bugs/894489

Title:
  Large result sets must return STATUS_WONT_HANDLE

Status in SQL Generator for testing SQL servers (MySQL, JavaDB, PostgreSQL):
  Fix Released

Bug description:
  If a random query produces a large dataset (usually seen with the db3
  and world datasets), the perl process will grow too big, causing OS
  thrashing.

  A solution would be to terminate the data retrieval loop and return a
  STATUS_WONT_HANDLE if more than 1 Gb of data has been processed (as
  measured by the size of the actual data structures).

To manage notifications about this bug go to:
https://bugs.launchpad.net/randgen/+bug/894489/+subscriptions