Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Can not create new primary key or unique constaraint with PgSQL 9.6 (RM #2397) #413

Open
dpage opened this issue May 12, 2017 · 1 comment
Labels

Comments

@dpage
Copy link
Contributor

dpage commented May 12, 2017

Issue migrated from Redmine: https://redmine.postgresql.org/issues/2397
Originally created by Maxim Zakharov at 2017-05-12 03:57:49 UTC.

The following error is shown when one tries to create an Unique Constraint for a table:

pgAdmin III

An error has occurred:

ERROR: column "amgettuple" does not exist
LINE 1: ..._am WHERE EXISTS (SELECT 1 FROM pg_proc WHERE oid=amgettuple...
^

OK

The same for new Primary Key index creation, see http://stackoverflow.com/questions/40904102/trying-to-set-constraint-new-primary-key-in-table-but-getting-an-error-colum

The patch attached solves this issue

@dpage
Copy link
Contributor Author

dpage commented May 12, 2017

Attachment migrated from Redmine: https://redmine.postgresql.org/attachments/download/2291
Originally created by Maxim Zakharov at 2017-05-12 03:57:15 UTC.

https://pgadmin-archive.postgresql.org/redmine/2397/2291-new-index-constaint.patch

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant