What problem are you facing?

We are building preview environments for an application and want to use a template database with STRATEGY=FILE_COPY. Today its not possible to add any strategy to Database when using template

This new feature from postgres enables ultra fast "branching"/"cloning" of databases even if the database i big (>50GB)

Postgres 18:

if the STRATEGY option is set to FILE_COPY, the method specified in file_copy_method will be used to copy files (commit f78ca6f3)

How could Crossplane help solve your problem?

Make a optional option for STRATEGY when creating a Database

Implementation (I would like to do, if design looks good to you)

Adding a new optional property on Database (postgresql.sql.m.crossplane.io) spec.forProvider.strategy with a enum options of clone or copy.