Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-08 Thread Torsten Krah
Am Mittwoch, dem 06.09.2023 um 20:42 +0200 schrieb Imre Samu: > Maybe you have to increase the "*--stop-timeout" value That is totally unrelated in my case, it is an anonymous volume anyway which gets created on start and deleted afterwards. Torsten

Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Imre Samu
> But how is that corruption happening - I mean it is a docker image, > freshly fetched from the registry. Hi Torsten, Maybe you have to increase the "*--stop-timeout" value ; ( or "*stop_grace_period" in docker-compose ) https://github.com/docker-library/postgres/issues/544#issuecomment-455738

Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Torsten Krah
Am Mittwoch, dem 06.09.2023 um 12:04 +0200 schrieb Erik Wienhold: > > I am running that one (official docker image) > > > > PostgreSQL 13.11 (Debian 13.11-1.pgdg110+1) on x86_64-pc-linux-gnu, > > compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit > > Have you also tried with 13.12? Yes, b

Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Erik Wienhold
ich should translate to something like: > > ERROR: duplicate key value violates unique constraint > "pg_statistic_relid_att_inh_index" > > DETAIL: Key (starelid, staattnum, stainherit)=(2609, 4, f) already exists. > > Anyone an idea what's wrong? > > Ma

Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Laurenz Albe
On Wed, 2023-09-06 at 10:33 +0200, Torsten Krah wrote: > Am Mittwoch, dem 06.09.2023 um 10:21 +0200 schrieb Laurenz Albe: > > You are lucky that the corrupted table is one that holds data that > > can be rebuilt. > > It is a test instance / container anyway which is deleted afterwards > and can be

Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Torsten Krah
Am Mittwoch, dem 06.09.2023 um 10:21 +0200 schrieb Laurenz Albe: > You are lucky that the corrupted table is one that holds data that > can be rebuilt. It is a test instance / container anyway which is deleted afterwards and can be setup again as often as I want. But how is that corruption happen

Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Laurenz Albe
nslate to something like: > > ERROR:  duplicate key value violates unique constraint > "pg_statistic_relid_att_inh_index" > > DETAIL:  Key (starelid, staattnum, stainherit)=(2609, 4, f) already exists. > > > Anyone an idea what's wrong? Yes: the metadata tab

running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"

2023-09-06 Thread Torsten Krah
lüsselwert verletzt Unique-Constraint »pg_statistic_relid_att_inh_index« Detail: Schlüssel »(starelid, staattnum, stainherit)=(2609, 4, f)« existiert bereits. which should translate to something like: ERROR: duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index&

duplicate key value violates unique constraint pg_default_acl_role_nsp_obj_index

2021-01-05 Thread Andrus
Hi! I have used script below to remove all rights from user and add some. Today it starts to throw error ERROR:  duplicate key value violates unique constraint "pg_default_acl_role_nsp_obj_index" DETAIL:  Key (defaclrole, defaclnamespace, defaclobjtype)=(30152, 186783649,

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-16 Thread Naresh Kumar
Thanks, I will check it out. On Fri 17 Jul, 2020, 7:42 AM Christophe Pettus > > > On Jul 16, 2020, at 19:08, Naresh Kumar wrote: > > > > Thanks Christopher, if you any such contacts can you share with us. > > The community maintains this page; I'm sure you can find someone who can > help you the

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-16 Thread Christophe Pettus
> On Jul 16, 2020, at 19:08, Naresh Kumar wrote: > > Thanks Christopher, if you any such contacts can you share with us. The community maintains this page; I'm sure you can find someone who can help you there: https://www.postgresql.org/support/professional_support/ -- -- Christoph

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-16 Thread Naresh Kumar
Thanks Christopher, if you any such contacts can you share with us. Regards, Narresh On Fri 17 Jul, 2020, 7:04 AM Christophe Pettus > > > On Jul 16, 2020, at 18:32, Naresh Kumar wrote: > > > > Can some one help us on this please. > > To be clear, what you almost certainly have here is serious d

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-16 Thread Christophe Pettus
> On Jul 16, 2020, at 18:32, Naresh Kumar wrote: > > Can some one help us on this please. To be clear, what you almost certainly have here is serious data corruption. You will need to find a (paid, commercial) specialist to help you with the recovery. You are unlikely to get the level of

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-16 Thread Naresh Kumar
Yes Karsten, Can some one help us on this please. Regards, Narresh On Wed 15 Jul, 2020, 10:55 PM Karsten Hilbert On Wed, Jul 15, 2020 at 10:03:06PM +0530, Naresh Kumar wrote: > > > Already I tried to connect with template0, template1, user database name, > > postgres, nothing is working getting

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-15 Thread Karsten Hilbert
On Wed, Jul 15, 2020 at 10:03:06PM +0530, Naresh Kumar wrote: > Already I tried to connect with template0, template1, user database name, > postgres, nothing is working getting same error message as mentioned in > trail mail. > > For the second one, yes we don't have backups to restore, we don't h

Re: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-15 Thread Naresh Kumar
Thanks Denial, Already I tried to connect with template0, template1, user database name, postgres, nothing is working getting same error message as mentioned in trail mail. For the second one, yes we don't have backups to restore, we don't have any option apart from data directory(no wal files)

RE: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-15 Thread Daniel Verite
TALLURI Nareshkumar wrote: > [0]postgres@axmdevhkdb008$ [PHKGAXMD008] psql > psql: FATAL: database "postgres" does not exist That's not necessarily a problem. The "postgres" database is generally empty and some installations don't even have one. Use "psql -d template1" instead, or s

RE: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-15 Thread TALLURI Nareshkumar
duplicate key value violates unique constraint "pg_namespace_nspname_index" Hello Postgres Support Team, Today we have an outage, our DB was wend down due to 100% space full at FS. We added space and could able to bring the cluster. DB version: psql (PostgreSQL) 10.12 OS version : Red

psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index"

2020-07-14 Thread TALLURI Nareshkumar
stgres | SQL_ASCII | C | C | =c/postgres +| 7513 kB | pg_default | default template for new databases | | | | | postgres=CTc/postgres | || (4 rows) But not able to create the schema: (postgres@[local]:5433)# [PHKGAXMP003]create schema

Re: duplicate key value violates unique constraint

2020-03-07 Thread Ron
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 -- 

Re: duplicate key value violates unique constraint

2020-03-07 Thread Adrian Klaver
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

duplicate key value violates unique constraint

2020-03-07 Thread Ashkar Dev
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 idusername ---- 1 abc 2 def 3 ghi if I delete all rows and insert one another it is like id

Re: duplicate key value violates unique constraint "chinese_price_infos_pkey"

2019-05-07 Thread Frank Alberto Rodriguez
e_infos" ("item_code", > "price_cents", "unit", "description", "company_id", "created_at", > "updated_at") VALUES ('01GS10001', 6000, 'Lift', 'Shore Crane > Rental', '9ae3f8b8

Re: duplicate key value violates unique constraint "chinese_price_infos_pkey"

2019-05-06 Thread Michael Nolan
On Mon, May 6, 2019 at 6:05 AM Arup Rakshit wrote: SELECT MAX(id) FROM chinese_price_infos; max 128520(1 row) SELECT nextval('chinese_price_infos_id_seq'); nextval - 71164(1 row) Not sure how it is out of sync. How can I fix this permanently. I ran vacuum analyze verbose;

Re: duplicate key value violates unique constraint "chinese_price_infos_pkey"

2019-05-06 Thread Ray O'Donnell
On 06/05/2019 12:10, Arup Rakshit wrote: Hi, Thanks for your reply. It is automatic, my app don’t creates ID, it delegates it to the DB. I am using Ruby on Rails app, where we use Postgresql. Well, I'm only throwing out wild guesses, but another possibility is that rows were loaded manually i

Re: duplicate key value violates unique constraint "chinese_price_infos_pkey"

2019-05-06 Thread Arup Rakshit
t;updated_at") VALUES ('01GS10001', 6000, 'Lift', 'Shore Crane >> Rental', '9ae3f8b8-8f3f-491c-918a-efd8f5100a5e', '2019-05-06 >> 10:49:03.894725', '2019-05-06 10:49:03.894725'); ERROR: duplicate >> key v

Re: duplicate key value violates unique constraint "chinese_price_infos_pkey"

2019-05-06 Thread Ray O'Donnell
ted_at") VALUES ('01GS10001', 6000, 'Lift', 'Shore Crane Rental', '9ae3f8b8-8f3f-491c-918a-efd8f5100a5e', '2019-05-06 10:49:03.894725', '2019-05-06 10:49:03.894725'); ERROR: duplicate key value violates unique constraint "chinese

duplicate key value violates unique constraint "chinese_price_infos_pkey"

2019-05-06 Thread Arup Rakshit
, 6000, 'Lift', 'Shore Crane Rental', '9ae3f8b8-8f3f-491c-918a-efd8f5100a5e', '2019-05-06 10:49:03.894725', '2019-05-06 10:49:03.894725'); ERROR: duplicate key value violates unique constraint "chinese_price_infos_pkey" DETA

Re: duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index" while performing full vacuum on the database

2018-05-09 Thread Laurenz Albe
Raghavendra Rao J S V wrote: > While performing vacuum full, I have received the below highlighted error. > Please guide me how to resolve this issue. > > > /opt/postgres/9.2/bin/psql -p 5433 --username=cmuser cpcm -c "VACUUM FULL > ANALYZE;" > > >

duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index" while performing full vacuum on the database

2018-05-09 Thread Raghavendra Rao J S V
Hi, While performing vacuum full, I have received the below highlighted error. Please guide me how to resolve this issue. ​/opt/postgres/9.2/bin/psql -p 5433 --username=cmuser cpcm -c "*VACUUM FULL ANALYZE*;" ERROR: *duplicate key value violates unique