anchor.diff:  <8> This means that we wait for the entities to be searchable before considering a write complete.
   On a production setup, the `write-sync` default will provide better performance.
   Using `sync` is especially important when testing as you need the entities to be searchable immediately.
  +<9> For development and tests, we rely on <<dev-services,Dev Services>>,
  +which means Quarkus will start a PostgreSQL database and Elasticsearch cluster automatically.
  +In production mode, however,
  +you will want to start a PostgreSQL database and Elasticsearch cluster manually,
  +which is why we provide Quarkus with this connection info in the `prod` profile (`%prod.` prefix).
   
   [TIP]
   For more information about the Hibernate Search extension configuration please refer to the <<configuration-reference, Configuration Reference>>.
  
positive.code: quarkus.ssl.native=false <1>
  
  quarkus.datasource.db-kind=postgresql <2>
  quarkus.datasource.username=quarkus_test
  quarkus.datasource.password=quarkus_test
  quarkus.datasource.jdbc.url=jdbc:postgresql:quarkus_test
  
  quarkus.hibernate-orm.database.generation=drop-and-create <3>
  quarkus.hibernate-orm.sql-load-script=import.sql <4>
  
negative.code: quarkus.hibernate-search-orm.elasticsearch.analysis.configurer=bean:myAnalysisConfigurer <6>
  quarkus.hibernate-search-orm.schema-management.strategy=drop-and-create <7>
  quarkus.hibernate-search-orm.automatic-indexing.synchronization.strategy=sync <8>
  
  %prod.quarkus.datasource.jdbc.url=jdbc:postgresql://localhost/quarkus_test <9>
  %prod.quarkus.datasource.username=quarkus_test
  %prod.quarkus.datasource.password=quarkus_test
  %prod.hibernate-search-orm.elasticsearch.hosts=localhost:9200 <9>
  ----
  <1> We won't use SSL so we disable it to have a more compact native executable.
  <2> Let's create a PostgreSQL datasource.
  