I use NHibernate 1.2.1.4 and Npgsql 0.7.1 database driver for data
access layer. From your comments it looks like these components are
responsible for INSERT statement creation (mostly NHibernate).
I think you can close this bug and I will search for solutions in
NHibernate community.
Gregor
"Oskars Ozols" <[EMAIL PROTECTED]> writes:
> id bigint NOT NULL DEFAULT
> nextval(('public.event_log_id_seq'::text)::regclass),
> 2008-07-15 12:32:03 EEST STATEMENT: INSERT INTO public.event_log
> (date_time, ip_address, action_type, severity, parameters, web_address,
> server, user_id, id)
"Oskars Ozols" <[EMAIL PROTECTED]> writes:
> I have noticed that during high load Postgre starts to use old free sequence
> values (like 156112 in my sample). Sometimes it's ok, but sometimes it fails
> with error above.
This is fairly hard to believe; the sequence code was debugged years
ago. Pa
The following bug has been logged online:
Bug reference: 4307
Logged by: Oskars Ozols
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: SuSE Linux Enterprise Server
Description:INSERT fails with primary key contraint
Details:
I have followin
