Re: [BUGS] Missing PRIMARY KEYs and duplicated rows
От | Chris Pacejo |
---|---|
Тема | Re: [BUGS] Missing PRIMARY KEYs and duplicated rows |
Дата | |
Msg-id | CAC8iE5ihe0C7XJ1bzdNTfjFeKsfHjUoUyoCA8BX1=Pcjm_1vSg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [BUGS] Missing PRIMARY KEYs and duplicated rows (Peter Geoghegan <pg@bowt.ie>) |
Список | pgsql-bugs |
On Wed, Apr 12, 2017 at 4:55 PM, Peter Geoghegan <pg@bowt.ie> wrote: > On Wed, Apr 12, 2017 at 1:46 PM, Chris Pacejo <cpacejo@clearskydata.com> wrote: >> All indexes are b-tree indexes. > > Can you show us the definition of all affected indexes? Any > discernible pattern to them? They are bog-standard b-trees created on behalf of a primary key, almost always an integer or bigint. E.g., from one of the unaffected databases: Indexes: "pk_databasechangeloglock" PRIMARY KEY, btree (id) The primary keys disappear from pg_class as well. The only pattern is that they're all in the same database. Which seems very strange to me; I'm having trouble thinking of what part of Postgres would affect both schema AND data in all tables of ONE database. If I remember correctly each table is stored in a separate file, and the WAL and server processes are shared across all databases. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: