[pgpool-general: 4177] documentation bug?

[Pablo Sanchez]

Hi everyone,

I think we might have a documentation bug.

As I understand the 'flow chart'[1], the following SELECT will not be
Load Balanced:

     START TRANSACTION
        SELECT * FROM my_table ...
     COMMIT;

The documentation states[2] when the JDBC driver's 'autocommit' option is
set to FALSE, it wraps all queries around a 'BEGIN' and 'COMMIT' and
thus they will not be Load Balanced.

I believe the documentation should read TRUE, not FALSE.

In Googling around[3], it seems when the JDBC driver's 'autocommit'
option is set to TRUE (not FALSE) is when each SQL is an implicit
transaction.

::: References :::

[1] - http://www.pgpool.net/docs/latest/where_to_send_queries.pdf

[2] - 
http://www.pgpool.net/docs/latest/pgpool-en.html#condition_for_load_balance

    Note: the JDBC driver has an autocommit option. If the autocommit is
    false, the JDBC driver sends "BEGIN" and "COMMIT" by itself. In this
    case the same restriction above regarding load balancing will be
    applied

[3]

o 
http://stackoverflow.com/questions/24683391/why-autocommit-is-by-default-false-in-hibernate-when-we-have-the-transaction-man

   - see the response (2)

o 
http://www.coderanch.com/t/463713/ORM/databases/disabling-autoCommit-hibernate
-- 
Pablo Sanchez - Blueoak Database Engineering, Inc
Ph:    819.459.1926         Blog:  http://pablo-blog.blueoakdb.com
iNum:  883.5100.0990.1054