agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feed"duplicate key value violates unique constraint" ERROR
13+ messages / 10 participants
[nested] [flat]
* "duplicate key value violates unique constraint" ERROR
@ 2010-05-05 10:22 Renato Oliveira <renato.oliveira@grant.co.uk>
0 siblings, 1 reply; 13+ messages in thread
From: Renato Oliveira @ 2010-05-05 10:22 UTC (permalink / raw)
To: pgsql-admin
Dear all,
I am sorry to have another post.
I have been following a problem which has been growing fast on our system.
At the beginning I thought it was related to load on PG server, then I thought it was load on the switch/network, now I don't know.
We seem to get loads of Exception errors and when I look at the Postgres Log there are loads of "duplicate key value violates unique constraint"
I have researched on the Internet and some posts say: Reindex, some say bug in JIRA.
Some say: Your primary key index isn't in sync.
Have you guys suffered from this problem before, or have seen it anywhere?
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: "duplicate key value violates unique constraint" ERROR
@ 2010-05-05 10:36 Ian Lea <ian.lea@gmail.com>
parent: Renato Oliveira <renato.oliveira@grant.co.uk>
0 siblings, 1 reply; 13+ messages in thread
From: Ian Lea @ 2010-05-05 10:36 UTC (permalink / raw)
To: Renato Oliveira <renato.oliveira@grant.co.uk>; +Cc: pgsql-admin
The most likely cause is surely application error: your application is
attempting to insert rows into a table and those new rows have the
primary key set to a value that is already present for that table.
Could be the app isn't checking properly before doing an insert (or
update), could be you are trying to load data twice, could be whatever
is generating the data in the first place is generating duplicates,
etc.
Seems unlikely that the exception itself would cause your system to
slow down but whatever is causing the exception (trying to load
everything multiple times?) might be.
--
Ian.
On Wed, May 5, 2010 at 11:22 AM, Renato Oliveira
<renato.oliveira@grant.co.uk> wrote:
> Dear all,
>
>
>
> I am sorry to have another post.
>
> I have been following a problem which has been growing fast on our system.
>
>
>
> At the beginning I thought it was related to load on PG server, then I
> thought it was load on the switch/network, now I don’t know.
>
>
>
> We seem to get loads of Exception errors and when I look at the Postgres Log
> there are loads of “duplicate key value violates unique constraint”
>
>
>
> I have researched on the Internet and some posts say: Reindex, some say bug
> in JIRA.
>
> Some say: Your primary key index isn't in sync.
>
>
>
> Have you guys suffered from this problem before, or have seen it anywhere?
>
>
>
> From 30th of April to today I got 1400 errors.
>
> What do you guys think might cause this behavior?
>
> I also think it is causing the system to slow down a bit, do you think that
> might be possible?
>
>
>
> Very much appreciate any help, insight, opinion or anything you could think.
>
>
>
> Thank you very much
>
>
>
>
>
> Best regards
>
>
>
> Renato
>
>
>
>
> Renato Oliveira
> Systems Administrator
> e-mail: renato.oliveira@grant.co.uk
>
> Tel: +44 (0)1763 260811
> Fax: +44 (0)1763 262410
> www.grant.co.uk
>
> Grant Instruments (Cambridge) Ltd
>
> Company registered in England, registration number 658133
>
> Registered office address:
> 29 Station Road,
> Shepreth,
> CAMBS SG8 6GB
> UK
>
>
>
>
>
>
>
> P Please consider the environment before printing this email
>
> CONFIDENTIALITY: The information in this e-mail and any attachments is
> confidential. It is intended only for the named recipients(s). If you are
> not the named recipient please notify the sender immediately and do not
> disclose the contents to another person or take copies.
>
> VIRUSES: The contents of this e-mail or attachment(s) may contain viruses
> which could damage your own computer system. Whilst Grant Instruments
> (Cambridge) Ltd has taken every reasonable precaution to minimise this risk,
> we cannot accept liability for any damage which you sustain as a result of
> software viruses. You should therefore carry out your own virus checks
> before opening the attachment(s).
>
> OpenXML: For information about the OpenXML file format in use within Grant
> Instruments please visit our website
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: "duplicate key value violates unique constraint" ERROR
@ 2010-05-05 11:02 Renato Oliveira <renato.oliveira@grant.co.uk>
parent: Ian Lea <ian.lea@gmail.com>
0 siblings, 0 replies; 13+ messages in thread
From: Renato Oliveira @ 2010-05-05 11:02 UTC (permalink / raw)
To: Ian Lea <ian.lea@gmail.com>; +Cc: pgsql-admin
Ian,
Thank you very much for your reply.
Really appreciated it.
Thank you
Renato
Renato Oliveira
Systems Administrator
e-mail: renato.oliveira@grant.co.uk
Tel: +44 (0)1763 260811
Fax: +44 (0)1763 262410
http://www.grant.co.uk/
Grant Instruments (Cambridge) Ltd
Company registered in England, registration number 658133
Registered office address:
29 Station Road,
Shepreth,
CAMBS SG8 6GB
UK
-----Original Message-----
From: Ian Lea [mailto:ian.lea@gmail.com]
Sent: 05 May 2010 11:36
To: Renato Oliveira
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] "duplicate key value violates unique constraint" ERROR
The most likely cause is surely application error: your application is
attempting to insert rows into a table and those new rows have the
primary key set to a value that is already present for that table.
Could be the app isn't checking properly before doing an insert (or
update), could be you are trying to load data twice, could be whatever
is generating the data in the first place is generating duplicates,
etc.
Seems unlikely that the exception itself would cause your system to
slow down but whatever is causing the exception (trying to load
everything multiple times?) might be.
--
Ian.
On Wed, May 5, 2010 at 11:22 AM, Renato Oliveira
<renato.oliveira@grant.co.uk> wrote:
> Dear all,
>
>
>
> I am sorry to have another post.
>
> I have been following a problem which has been growing fast on our system.
>
>
>
> At the beginning I thought it was related to load on PG server, then I
> thought it was load on the switch/network, now I don't know.
>
>
>
> We seem to get loads of Exception errors and when I look at the Postgres Log
> there are loads of "duplicate key value violates unique constraint"
>
>
>
> I have researched on the Internet and some posts say: Reindex, some say bug
> in JIRA.
>
> Some say: Your primary key index isn't in sync.
>
>
>
> Have you guys suffered from this problem before, or have seen it anywhere?
>
>
>
> From 30th of April to today I got 1400 errors.
>
> What do you guys think might cause this behavior?
>
> I also think it is causing the system to slow down a bit, do you think that
> might be possible?
>
>
>
> Very much appreciate any help, insight, opinion or anything you could think.
>
>
>
> Thank you very much
>
>
>
>
>
> Best regards
>
>
>
> Renato
>
>
>
>
> Renato Oliveira
> Systems Administrator
> e-mail: renato.oliveira@grant.co.uk
>
> Tel: +44 (0)1763 260811
> Fax: +44 (0)1763 262410
> www.grant.co.uk
>
> Grant Instruments (Cambridge) Ltd
>
> Company registered in England, registration number 658133
>
> Registered office address:
> 29 Station Road,
> Shepreth,
> CAMBS SG8 6GB
> UK
>
>
>
>
>
>
>
> P Please consider the environment before printing this email
>
> CONFIDENTIALITY: The information in this e-mail and any attachments is
> confidential. It is intended only for the named recipients(s). If you are
> not the named recipient please notify the sender immediately and do not
> disclose the contents to another person or take copies.
>
> VIRUSES: The contents of this e-mail or attachment(s) may contain viruses
> which could damage your own computer system. Whilst Grant Instruments
> (Cambridge) Ltd has taken every reasonable precaution to minimise this risk,
> we cannot accept liability for any damage which you sustain as a result of
> software viruses. You should therefore carry out your own virus checks
> before opening the attachment(s).
>
> OpenXML: For information about the OpenXML file format in use within Grant
> Instruments please visit our website
-----Original Message-----
P Please consider the environment before printing this email
CONFIDENTIALITY: The information in this e-mail and any attachments is confidential. It is intended only for the named recipients(s). If you are not the named recipient please notify the sender immediately and do not disclose the contents to another person or take copies.
VIRUSES: The contents of this e-mail or attachment(s) may contain viruses which could damage your own computer system. Whilst Grant Instruments (Cambridge) Ltd has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should therefore carry out your own virus checks before opening the attachment(s).
OpenXML: For information about the OpenXML file format in use within Grant Instruments please visit our http://www.grant.co.uk/Support/openxml.html
^ permalink raw reply [nested|flat] 13+ messages in thread
* duplicate key value violates unique constraint
@ 2020-03-07 19:29 Ashkar Dev <ashkardev@gmail.com>
0 siblings, 3 replies; 13+ messages in thread
From: Ashkar Dev @ 2020-03-07 19:29 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Hi all,
how to fix a problem, suppose there is a table with id and username
if I set the id to bigint so the limit is 9223372036854775807
if I insert for example 3 rows
id username
-- --------------
1 abc
2 def
3 ghi
if I delete all rows and insert one another it is like
id username
-- --------------
4 jkl
So it doesn't start again from non-available id 1, so what is needed to do
to make the new inserts go into non-available id numbers?
^ permalink raw reply [nested|flat] 13+ messages in thread
* Fwd: duplicate key value violates unique constraint
@ 2020-03-07 19:35 Ashkar Dev <ashkardev@gmail.com>
parent: Ashkar Dev <ashkardev@gmail.com>
2 siblings, 2 replies; 13+ messages in thread
From: Ashkar Dev @ 2020-03-07 19:35 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi all,
how to fix a problem, suppose there is a table with id and username
if I set the id to bigint so the limit is 9223372036854775807
if I insert for example 3 rows
id username
-- --------------
1 abc
2 def
3 ghi
if I delete all rows and insert one another it is like
id username
-- --------------
4 jkl
So it doesn't start again from non-available id 1, so what is needed to do
to make the new inserts go into non-available id numbers?
and if the id reaches the limit and maybe there is some ids that are not
used.
^ permalink raw reply [nested|flat] 13+ messages in thread
* RE: duplicate key value violates unique constraint
@ 2020-03-07 19:54 Dave Bolt <dave@davebolt.co.uk>
parent: Ashkar Dev <ashkardev@gmail.com>
1 sibling, 0 replies; 13+ messages in thread
From: Dave Bolt @ 2020-03-07 19:54 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org; +Cc: 'Ashkar Dev' <ashkardev@gmail.com>
I have two immediate questions on this.
1) Do you Need to make sure there are no gaps in the sequence of id values?
2) Are you ever going to use 9223372036854775807 id values, even with the deletions?
If you want to re-use the id of a deleted row, and it is not going to cause problems elsewhere in your database, you could always have a deleted column in each row instead of actually removing from the table. When you want to insert next, you would just look for the first row where deleted is true and replace it.
Not entirely perfect, but would probably do the job.
From: Ashkar Dev [mailto:ashkardev@gmail.com]
Sent: 07 March 2020 19:35
To: pgsql-admin@lists.postgresql.org
Subject: Fwd: duplicate key value violates unique constraint
Hi all,
how to fix a problem, suppose there is a table with id and username
if I set the id to bigint so the limit is 9223372036854775807
if I insert for example 3 rows
id username
-- --------------
1 abc
2 def
3 ghi
if I delete all rows and insert one another it is like
id username
-- --------------
4 jkl
So it doesn't start again from non-available id 1, so what is needed to do to make the new inserts go into non-available id numbers?
and if the id reaches the limit and maybe there is some ids that are not used.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: duplicate key value violates unique constraint
@ 2020-03-07 19:55 David G. Johnston <david.g.johnston@gmail.com>
parent: Ashkar Dev <ashkardev@gmail.com>
1 sibling, 1 reply; 13+ messages in thread
From: David G. Johnston @ 2020-03-07 19:55 UTC (permalink / raw)
To: Ashkar Dev <ashkardev@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Sat, Mar 7, 2020 at 12:35 PM Ashkar Dev <ashkardev@gmail.com> wrote:
>
> Hi all,
>
> how to fix a problem, suppose there is a table with id and username
>
You should probably provide the definition though in this case it is
self-evident that you are using bigserial.
> So it doesn't start again from non-available id 1, so what is needed to do
> to make the new inserts go into non-available id numbers?
>
Alter sequence
https://www.postgresql.org/docs/12/sql-altersequence.html
> and if the id reaches the limit and maybe there is some ids that are not
> used.
>
This is highly unlikely.
Is the subject line supposed to relate to this in some way?
You should not worry about any of this in production; and frankly, worrying
about it in development is largely pointless as well.
There is no actual problem here to be fixed.
David J.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: duplicate key value violates unique constraint
@ 2020-03-07 20:21 Ashkar Dev <ashkardev@gmail.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 0 replies; 13+ messages in thread
From: Ashkar Dev @ 2020-03-07 20:21 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; dave@davebolt.co.uk, Pepe TD Vo <pepevo@yahoo.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Thanks for answers.
On Sat, Mar 7, 2020 at 10:55 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:
> On Sat, Mar 7, 2020 at 12:35 PM Ashkar Dev <ashkardev@gmail.com> wrote:
>
>>
>> Hi all,
>>
>> how to fix a problem, suppose there is a table with id and username
>>
>
> You should probably provide the definition though in this case it is
> self-evident that you are using bigserial.
>
>
>> So it doesn't start again from non-available id 1, so what is needed to
>> do to make the new inserts go into non-available id numbers?
>>
>
> Alter sequence
>
> https://www.postgresql.org/docs/12/sql-altersequence.html
>
>
>> and if the id reaches the limit and maybe there is some ids that are not
>> used.
>>
>
> This is highly unlikely.
>
> Is the subject line supposed to relate to this in some way?
>
> You should not worry about any of this in production; and frankly,
> worrying about it in development is largely pointless as well.
>
> There is no actual problem here to be fixed.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: duplicate key value violates unique constraint
@ 2020-03-07 20:28 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Ashkar Dev <ashkardev@gmail.com>
2 siblings, 0 replies; 13+ messages in thread
From: Adrian Klaver @ 2020-03-07 20:28 UTC (permalink / raw)
To: Ashkar Dev <ashkardev@gmail.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
On 3/7/20 11:29 AM, Ashkar Dev wrote:
> Hi all,
>
> how to fix a problem, suppose there is a table with id and username
>
> if I set the id to bigint so the limit is 9223372036854775807
> if I insert for example 3 rows
> id username
> -- --------------
> 1 abc
> 2 def
> 3 ghi
>
> if I delete all rows and insert one another it is like
>
> id username
> -- --------------
> 4 jkl
So I am assuming id is of type bigserial or something that has a
sequence behind it?
>
>
> So it doesn't start again from non-available id 1, so what is needed to
> do to make the new inserts go into non-available id numbers?
If you are sequences then they do not go backwards:
https://www.postgresql.org/docs/12/sql-createsequence.html
"Because nextval and setval calls are never rolled back, sequence
objects cannot be used if “gapless” assignment of sequence numbers is
needed. It is possible to build gapless assignment by using exclusive
locking of a table containing a counter; but this solution is much more
expensive than sequence objects, especially if many transactions need
sequence numbers concurrently."
If you want that to happen you will have to roll your own implementation.
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: duplicate key value violates unique constraint
@ 2020-03-07 21:13 Ron <ronljohnsonjr@gmail.com>
parent: Ashkar Dev <ashkardev@gmail.com>
2 siblings, 0 replies; 13+ messages in thread
From: Ron @ 2020-03-07 21:13 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
Asking the same question on multiple lists is strongly frowned upon.
On 3/7/20 1:29 PM, Ashkar Dev wrote:
> Hi all,
>
> how to fix a problem, suppose there is a table with id and username
>
> if I set the id to bigint so the limit is 9223372036854775807
> if I insert for example 3 rows
> id username
> -- --------------
> 1 abc
> 2 def
> 3 ghi
>
> if I delete all rows and insert one another it is like
>
> id username
> -- --------------
> 4 jkl
>
>
> So it doesn't start again from non-available id 1, so what is needed to do
> to make the new inserts go into non-available id numbers?
--
Angular momentum makes the world go 'round.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error
@ 2026-02-19 01:47 Ed Sabol <edwardjsabol@gmail.com>
0 siblings, 1 reply; 13+ messages in thread
From: Ed Sabol @ 2026-02-19 01:47 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Using PostgreSQL 15.16, I have some SQL for creating a materialized view that's inside a larger transaction which randomly emits the following error:
ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
DETAIL: Key (typname, typnamespace)=(largetable, 20488) already exists.
The error doesn't happen 100% of the times I try to execute this transaction. Maybe 30% of the time? Also, I've had it happen on multiple separate PostgreSQL servers.
I'm not entirely sure how to interpret these ERROR and DETAIL messages. Can someone explain it?
I've tried the following queries to try to figure out what typnamespace = 20488 refers to:
SELECT nspname FROM pg_namespace WHERE oid = 20488;
SELECT count(*) FROM pg_catalog.pg_type WHERE typname = 'targetable' AND typnamespace = 20488;
Neither query provides any useful information. The latter always returns zero immediately immediately prior to the SQL error.
Here's the (slightly sanitized) SQL which causes the error:
CREATE MATERIALIZED VIEW someschema.largetable AS
(
SELECT
row_number() OVER () AS __row,
sub.*,
public.somefunc1(afield) AS s_result1,
public.somefunc2(anotherfield) AS s_result2,
public.somefunc3(somefield1, somefield2) AS s_result3
FROM (
SELECT * FROM someschema.largetable_upd_1
UNION ALL SELECT * FROM someschema.largetable_upd_2
UNION ALL SELECT * FROM someschema.largetable_upd_3
UNION ALL SELECT * FROM someschema.largetable_upd_4
UNION ALL SELECT * FROM someschema.largetable_upd_5
UNION ALL SELECT * FROM someschema.largetable_upd_6
UNION ALL SELECT * FROM someschema.largetable_upd_8
UNION ALL SELECT * FROM someschema.largetable_upd_9
UNION ALL SELECT * FROM someschema.largetable_upd_10
) sub
);
public.somefunc1, public.somefunc2, and public.somefunc3 return three types defined in PgSphere. I have the latest PgSphere installed.
Any ideas as to how to eliminate the error?
My first thought was to change the asterisks to explicit lists of columns.
Any assistance would be appreciated!
Thanks,
Ed
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error
@ 2026-02-19 04:51 Tom Lane <tgl@sss.pgh.pa.us>
parent: Ed Sabol <edwardjsabol@gmail.com>
0 siblings, 1 reply; 13+ messages in thread
From: Tom Lane @ 2026-02-19 04:51 UTC (permalink / raw)
To: Ed Sabol <edwardjsabol@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Ed Sabol <edwardjsabol@gmail.com> writes:
> Using PostgreSQL 15.16, I have some SQL for creating a materialized view that's inside a larger transaction which randomly emits the following error:
> ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
> DETAIL: Key (typname, typnamespace)=(largetable, 20488) already exists.
Huh. Does it always mention 20488?
> I've tried the following queries to try to figure out what typnamespace = 20488 refers to:
> SELECT nspname FROM pg_namespace WHERE oid = 20488;
> SELECT count(*) FROM pg_catalog.pg_type WHERE typname = 'targetable' AND typnamespace = 20488;
> Neither query provides any useful information.
What do you mean by "any useful information", exactly? Do these show
that there is no pg_namespace row with oid = 20488?
If that is the case, I'd bet on index corruption in the indexes of
pg_type and/or pg_namespace. REINDEX might help.
regards, tom lane
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error
@ 2026-02-19 13:02 Edward J. Sabol <edwardjsabol@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 13+ messages in thread
From: Edward J. Sabol @ 2026-02-19 13:02 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Feb 18, 2026, at 11:51 PM, Tom Lane wrote:
> Ed Sabol <edwardjsabol@gmail.com> writes:
>> Using PostgreSQL 15.16, I have some SQL for creating a materialized view that's inside a larger transaction which randomly emits the following error:
>> ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
>> DETAIL: Key (typname, typnamespace)=(largetable, 20488) already exists.
>
> Huh. Does it always mention 20488?
Yes, it's always 20488.
>> I've tried the following queries to try to figure out what typnamespace = 20488 refers to:
>
>> SELECT nspname FROM pg_namespace WHERE oid = 20488;
>> SELECT count(*) FROM pg_catalog.pg_type WHERE typname = 'targetable' AND typnamespace = 20488;
>
>> Neither query provides any useful information.
>
> What do you mean by "any useful information", exactly? Do these show
> that there is no pg_namespace row with oid = 20488?
Well, the first query returns a schema that is completely unrelated to anything the SQL is doing. I wondered if the typnamespace = 20488 DETAIL was referring to something else.
> If that is the case, I'd bet on index corruption in the indexes of
> pg_type and/or pg_namespace. REINDEX might help.
I'll try that. But why would it only happen sometimes?
All of the mentions of this error message I could find on the Internet suggest this happens when you have multiple processes trying to execute the same DDL simultaneously, but I'm sure there's only one process executing this transaction.
Thanks,
Ed
^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2026-02-19 13:02 UTC | newest]
Thread overview: 13+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-05-05 10:22 "duplicate key value violates unique constraint" ERROR Renato Oliveira <renato.oliveira@grant.co.uk>
2010-05-05 10:36 ` Ian Lea <ian.lea@gmail.com>
2010-05-05 11:02 ` Renato Oliveira <renato.oliveira@grant.co.uk>
2020-03-07 19:29 duplicate key value violates unique constraint Ashkar Dev <ashkardev@gmail.com>
2020-03-07 19:35 ` Fwd: duplicate key value violates unique constraint Ashkar Dev <ashkardev@gmail.com>
2020-03-07 19:54 ` RE: duplicate key value violates unique constraint Dave Bolt <dave@davebolt.co.uk>
2020-03-07 19:55 ` Re: duplicate key value violates unique constraint David G. Johnston <david.g.johnston@gmail.com>
2020-03-07 20:21 ` Re: duplicate key value violates unique constraint Ashkar Dev <ashkardev@gmail.com>
2020-03-07 20:28 ` Re: duplicate key value violates unique constraint Adrian Klaver <adrian.klaver@aklaver.com>
2020-03-07 21:13 ` Re: duplicate key value violates unique constraint Ron <ronljohnsonjr@gmail.com>
2026-02-19 01:47 Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error Ed Sabol <edwardjsabol@gmail.com>
2026-02-19 04:51 ` Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error Tom Lane <tgl@sss.pgh.pa.us>
2026-02-19 13:02 ` Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error Edward J. Sabol <edwardjsabol@gmail.com>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox