Rails Unique Key Violation with Multiple Instances
up vote
0
down vote
favorite
I am using this gem:
https://github.com/rails/activerecord-session_store
When I run multiple instances of the rails app, I get this error occurring:
PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "sessions_pkey"
DETAIL: Key (id)=(3005307) already exists.
: INSERT INTO "sessions" ("session_id", "data", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"
The id column is generated by a sequence:
CREATE TABLE public.sessions
(
id integer NOT NULL DEFAULT nextval('sessions_id_seq'::regclass),
session_id character varying(255) COLLATE pg_catalog."default" NOT NULL,
data text COLLATE pg_catalog."default",
created_at timestamp without time zone,
updated_at timestamp without time zone,
CONSTRAINT sessions_pkey PRIMARY KEY (id)
)
WITH (
OIDS = FALSE
)
TABLESPACE pg_default;
Given this is the case, shouldn't the sequence guarantee uniqueness even if the inserts are happening from multiple processes?
ruby-on-rails postgresql
add a comment |
up vote
0
down vote
favorite
I am using this gem:
https://github.com/rails/activerecord-session_store
When I run multiple instances of the rails app, I get this error occurring:
PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "sessions_pkey"
DETAIL: Key (id)=(3005307) already exists.
: INSERT INTO "sessions" ("session_id", "data", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"
The id column is generated by a sequence:
CREATE TABLE public.sessions
(
id integer NOT NULL DEFAULT nextval('sessions_id_seq'::regclass),
session_id character varying(255) COLLATE pg_catalog."default" NOT NULL,
data text COLLATE pg_catalog."default",
created_at timestamp without time zone,
updated_at timestamp without time zone,
CONSTRAINT sessions_pkey PRIMARY KEY (id)
)
WITH (
OIDS = FALSE
)
TABLESPACE pg_default;
Given this is the case, shouldn't the sequence guarantee uniqueness even if the inserts are happening from multiple processes?
ruby-on-rails postgresql
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using this gem:
https://github.com/rails/activerecord-session_store
When I run multiple instances of the rails app, I get this error occurring:
PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "sessions_pkey"
DETAIL: Key (id)=(3005307) already exists.
: INSERT INTO "sessions" ("session_id", "data", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"
The id column is generated by a sequence:
CREATE TABLE public.sessions
(
id integer NOT NULL DEFAULT nextval('sessions_id_seq'::regclass),
session_id character varying(255) COLLATE pg_catalog."default" NOT NULL,
data text COLLATE pg_catalog."default",
created_at timestamp without time zone,
updated_at timestamp without time zone,
CONSTRAINT sessions_pkey PRIMARY KEY (id)
)
WITH (
OIDS = FALSE
)
TABLESPACE pg_default;
Given this is the case, shouldn't the sequence guarantee uniqueness even if the inserts are happening from multiple processes?
ruby-on-rails postgresql
I am using this gem:
https://github.com/rails/activerecord-session_store
When I run multiple instances of the rails app, I get this error occurring:
PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "sessions_pkey"
DETAIL: Key (id)=(3005307) already exists.
: INSERT INTO "sessions" ("session_id", "data", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"
The id column is generated by a sequence:
CREATE TABLE public.sessions
(
id integer NOT NULL DEFAULT nextval('sessions_id_seq'::regclass),
session_id character varying(255) COLLATE pg_catalog."default" NOT NULL,
data text COLLATE pg_catalog."default",
created_at timestamp without time zone,
updated_at timestamp without time zone,
CONSTRAINT sessions_pkey PRIMARY KEY (id)
)
WITH (
OIDS = FALSE
)
TABLESPACE pg_default;
Given this is the case, shouldn't the sequence guarantee uniqueness even if the inserts are happening from multiple processes?
ruby-on-rails postgresql
ruby-on-rails postgresql
asked Nov 20 at 2:28
zorro2b
1,12821832
1,12821832
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385358%2frails-unique-key-violation-with-multiple-instances%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown