Re: Disabling/Enabling index before bulk loading
| От | Nikolay Samokhvalov |
|---|---|
| Тема | Re: Disabling/Enabling index before bulk loading |
| Дата | |
| Msg-id | CANNMO+LQ5sdWyH_+N9Zjah2W5+cvXRYtUnya0+GCwVGVhfjr-w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Disabling/Enabling index before bulk loading (Ravi Krishna <srkrishna@yahoo.com>) |
| Список | pgsql-general |
On Tue, Jul 10, 2018 at 12:26 PM Ravi Krishna <srkrishna@yahoo.com> wrote:
This does not work in RDS. In order to update system catalog tables (pg_index), one needs privileges which isdenied in RDS. In RDS terminology, the user must belong to role rdsadmin and that role is reserved only for AWSinternal users.
Right, but pl/pgsql works fine there, so you can backup&drop all indexes and then restore them using `do $$ ... $$ language plpgsql;`, as Thomas Kellerer already suggested.
One note here: there is some old confusion between concepts of unique indexes and unique constraints in Postgres (see https://www.postgresql.org/message-id/flat/CANNMO%2BKHkkDg-FBi0_78ADmfLiT9kODmz%2B8m6fR6f5kPL-n_ZQ%40mail.gmail.com#cfb3a9eaed8649d7d24ad7944ccb37cf), so there is a chance that after such backup/restore procedure you'll get logically correct but phisically different state.
В списке pgsql-general по дате отправления: