How to prevent SELECT queries from SequenceGenerator

If I use the pooled SequenceGenerator

 @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "my_seq")
 @SequenceGenerator(name = "my_seq", sequenceName = "my_seq", allocationSize = 10)

then my query assertions fail sometimes, because due to the pooling, the statement(s)

select nextval ('my_seq')

are sometimes called before and sometimes during the test.

It works, when I change this property to none

spring.jpa.properties.hibernate.id.optimizer.pooled.preferred=none

Is this approach recommended or is there a better way to assert query count when using pooled sequence generator?

[krupt]

For our project, I wrote an exclusion listener. Works like a charm:

...
ProxyDataSource proxyDataSource = new ProxyDataSource(dataSource);
proxyDataSource.addListener(new ExcludeSelectSequenceFromStatisticQueryCountListener());

class ExcludeSelectSequenceFromStatisticQueryCountListener extends DataSourceQueryCountListener {

    private static final Pattern SELECT_SEQUENCE_PATTERN =
        Pattern.compile("select\\s.*nextval\\s\\('.*'\\)",
                        Pattern.CASE_INSENSITIVE & Pattern.MULTILINE);

    @Override
    public void afterQuery(ExecutionInfo execInfo, List<QueryInfo> queryInfoList) {
        final List<QueryInfo> newQueryInfoList = queryInfoList.stream()
            .filter(it -> !SELECT_SEQUENCE_PATTERN.matcher(it.getQuery()).matches())
            .collect(Collectors.toList());

        super.afterQuery(execInfo, newQueryInfoList);
    }
}

[vladmihalcea]

It’s not a good idea to disable identifier optimizers. The same select queries are executed in production too, so you should check the actual statement count.