Hi all,
Thanks Greg and Daniel for the helpful feedback and suggestions.
Following your advice, we're considering moving PGroonga's database-specific
files out of the `base/` directory to avoid interference with `pg_checksums`.
Specifically, we're exploring placing them under a path such as
`pgroonga/${DB_OID}/pgrn*`.
This approach would likely resolve the checksum verification issue without
requiring any PostgreSQL changes.
Here's a brief summary of what we've verified so far:
- Files under `base/` indeed trigger `pg_checksums` verification failures.
- Moving the same files to `$PGDATA/pgroonga/` allowed checksum verification to
complete successfully.
- `pg_basebackup` includes files and directories placed directly under the
PostgreSQL data directory, not only `base/`. So our proposed new location
would still be included in backups.
- According to the PostgreSQL source code, `pg_checksums` checks only the
following directories. Therefore, files under `$PGDATA/pgroonga/` are safely
excluded.
- `global/`
- `base/`
- `pg_tblspc/`
We'll continue testing this approach to confirm compatibility and performance
before finalizing the change.
Thanks again for the discussion and insights that helped guide our direction.
Best regards,
Yasuhiro Horimoto
PGroonga Team
