> and even wrap around completely. Since the row lock is ignored by nextval > and setval, the usefulness of the operation is highly debatable anyway.
As for pgpool, this is plain wrong. The reason why pgpool uses sequene row lock is to obtain sequence table lock like effect, which is not currently permitted. Whether nextval and setval ignore sequence row lock is irrelevant. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
