Re: pg_dump: could not parse ACL list
| От | Tom Lane |
|---|---|
| Тема | Re: pg_dump: could not parse ACL list |
| Дата | |
| Msg-id | 20591.1091812778@sss.pgh.pa.us обсуждение |
| Ответ на | pg_dump: could not parse ACL list (Gaetano Mendola <mendola@bigfoot.com>) |
| Ответы |
Re: pg_dump: could not parse ACL list
Re: pg_dump: could not parse ACL list |
| Список | pgsql-hackers |
Gaetano Mendola <mendola@bigfoot.com> writes:
> $ pg_dump -p 5433 test
> pg_dump: could not parse ACL list ([0:1]={postgres=UC/postgres,=UC/postgres}) for object "public" (SCHEMA)
Ugh. This is an unforeseen side effect of Joe's recent changes to make
array_out emit dimension info.
I think the most reasonable answer is to tweak the ACL code so that it
creates ACL arrays with lower bound 1 instead of lower bound 0. The
only possible downside is that this would confuse any client code that
is manually manipulating ACL arrays and knows about the lower-bound-0
behavior ... but any such code is likely broken anyway by the other ACL
changes that have gone on lately ...
regards, tom lane
В списке pgsql-hackers по дате отправления: