Hi @Marvin I use aws rds with proxy. I get this error in the server: "RDS Proxy currently doesn't support the option jit."

It seems that there are no issues reported in the Prefect GitHub repository related to the specific error "RDS Proxy currently doesn't support the option jit." However, the error message suggests that your configuration includes enabling Just-In-Time (JIT) compilation which is not supported by AWS RDS Proxy. To resolve this issue, you would typically need to disable JIT in your database configuration. This setting is specific to the database engine you're using (like PostgreSQL), so you would adjust it accordingly in your database parameters. Since this doesn't seem to be a Prefect-specific issue but rather related to AWS RDS Proxy, I recommend checking the AWS RDS documentation or forums for guidance on how to disable JIT in your RDS configuration, or contacting AWS support for further assistance. If the issue is persisting in the context of a Prefect deployment or interaction with RDS through Prefect, please provide more details about how Prefect is being used with AWS RDS in your setup. This would help in giving a more accurate resolution to the problem.

Is it possible to disable JIT in prefect?

It appears that Prefect itself does not provide an explicit setting to enable or disable Just-In-Time (JIT) compilation because JIT is a feature specific to certain database systems like PostgreSQL. Prefect integrates with databases but does not manage their internal configurations such as JIT. Prefect supports using external databases like PostgreSQL for orchestration backend needs, and if JIT needs to be disabled, it should be done through the database's own configuration. For instance, if PostgreSQL is used, you would adjust the JIT settings in the PostgreSQL configuration file (usually

postgresql.conf

) or through SQL commands executed against the database. Here's a general guide on how to disable JIT in PostgreSQL, which you may need to adapt based on your specific database version and setup:

sql
-- To disable JIT for an individual session:
SET jit = off;

-- To disable JIT for the entire PostgreSQL instance:
ALTER SYSTEM SET jit = off;

Please note that after altering system-level configurations, you often need to restart the database server for the changes to take effect. If your Prefect deployment is facing issues due to JIT being enabled in the connected database, adjusting these settings in the database itself should be the course of action, rather than attempting to adjust JIT behavior from within Prefect. If there is a specific context within Prefect where JIT is causing an issue, please provide additional details, and I'll be happy to explore further solutions.