gh-92434: Silence a compiler warning in _sqlite/connection.c for 32bit version

[neonene]

MSVC emits a possible loss of data warning when building 32bit version of _sqlite3.Connection.serialize(), whose data size is should be limited to 0x7fffffff in sqlite-3.38.4.0/sqlite3.c, even on 64bit python (EDIT: Sorry, I missed the pages):

SQLITE_PRIVATE void *sqlite3Malloc(u64 n){
  void *p;
  if( n==0 || n>=0x7fffff00 ){
    /* A memory allocation of a number of bytes which is near the maximum
    ** signed integer value might cause an integer overflow inside of the
    ** xMalloc().  Hence we limit the maximum size to 0x7fffff00, giving
    ** 255 bytes of overhead.  SQLite itself will never use anything near
    ** this amount.  The only way to reach the limit is with sqlite3_malloc() */
    p = 0;
  }else if( sqlite3GlobalConfig.bMemstat ){
    ...

#92434

[erlend-aasland]

Thanks for you PR, @neonene, and thanks for sorting out the nitty gritty details, Kumar! If there are still unresolved issues, please open a new issue in the bug tracker.

[miss-islington]

Thanks @neonene for the PR, and @erlend-aasland for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛏🤖

[bedevere-bot]

GH-93672 is a backport of this pull request to the 3.11 branch.

[neonene]

@kumaraditya303 Do you know the possibility around Py_SSIZE_T_MAX(2G) bytes, not more than 4GB?

[kumaraditya303]

Do you know the possibility around Py_SSIZE_T_MAX(2G) bytes, not more than 4GB?

Please create a new issue to discuss this.