[Pgpool-general] pgpool-II 3.1 released

[Lonni J Friedman]

On Thu, Sep 8, 2011 at 5:30 AM, Toshihiro Kitagawa
<kitagawa at sraoss.co.jp> wrote:
> - Change the lock method of insert_lock. The previous insert_lock uses
>  row locking against the sequence relation, but the current one uses
>  row locking against pgpool_catalog.insert_lock table. The reason is
>  that PostgreSQL core developers decided to disallow row locking
>  against the sequence relation to avoid an internal error which it
>  leads. So creating insert_lock table in all databases which are
>  accessed via pgpool-II beforehand is required. If does not exist
>  insert_lock table, pgpool-II locks the insert target table. This
>  behavior is same as pgpool-II 2.2 and 2.3 series. If you want to use
>  insert_lock which is compatible with older releases, you can specify
>  lock method by configure options: --enable-sequence-lock,
>  --enable-table-lock(Kitagawa)

Is there a sql script somewhere for creating this table with the
correct/expected schema?