's not related to the bigserial primary key.
aah, stupid me. thank you!
ok, then back to coova-chilli :)
peter
--
:: e n d i a n
:: security with passion
:: peter warasin
:: http://www.endian.com :: pe...@endian.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.or
happens only from
time to time.
it must be related to load. when the system is under heavy load
something goes wrong and 2 concurrent transactions get the same unique
id. but how??
peter
--
:: e n d i a n
:: security with passion
:: peter warasin
:: http://www.endian.com :: pe...@endian.c
: e n d i a n
:: security with passion
:: peter warasin
:: http://www.endian.com :: pe...@endian.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
: e n d i a n
:: security with passion
:: peter warasin
:: http://www.endian.com :: pe...@endian.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
