CRAN Package Check Results for Package RPostgreSQL

Last updated on 2026-04-24 17:50:19 CEST.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	0.7-8	9.15	40.01	49.16	OK
r-devel-linux-x86_64-debian-gcc	0.7-8	6.92	31.42	38.34	OK
r-devel-linux-x86_64-fedora-clang	0.7-8	13.00	60.11	73.11	OK
r-devel-linux-x86_64-fedora-gcc	0.7-8	14.00	58.98	72.98	OK
r-patched-linux-x86_64	0.7-8	9.32	37.87	47.19	OK
r-release-linux-x86_64	0.7-8	8.07	35.11	43.18	OK
r-release-macos-arm64	0.7-8	5.00	13.00	18.00	WARN
r-release-macos-x86_64	0.7-8	15.00	59.00	74.00	WARN
r-release-windows-x86_64	0.7-8	26.00	123.00	149.00	OK
r-oldrel-macos-arm64	0.7-8				WARN
r-oldrel-macos-x86_64	0.7-8	13.00	35.00	48.00	WARN
r-oldrel-windows-x86_64	0.7-8	28.00	119.00	147.00	OK

Additional issues

rchk

Check Details

Version: 0.7-8
Check: compiled code
Result: WARN File ‘RPostgreSQL/libs/RPostgreSQL.so’: Found ‘___sprintf_chk’, possibly from ‘sprintf’ (C) Object: ‘libpq/libpq.a’ Found ‘___stderrp’, possibly from ‘stderr’ (C) Object: ‘libpq/libpq.a’ Found ‘_abort’, possibly from ‘abort’ (C) Object: ‘libpq/libpq.a’ Found ‘_sprintf’, possibly from ‘sprintf’ (C) Object: ‘libpq/libpq.a’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64