Re: pg_dump: could not parse ACL list
| От | Joe Conway |
|---|---|
| Тема | Re: pg_dump: could not parse ACL list |
| Дата | |
| Msg-id | 4113EEB3.5010308@joeconway.com обсуждение исходный текст |
| Ответ на | Re: pg_dump: could not parse ACL list (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
Tom Lane wrote:
> 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.
Sorry about that :(. I guess I haven't tried dumping any databases since
making the change.
> 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 ...
At least it looks like it was an easy fix :).
Thanks,
Joe
В списке pgsql-hackers по дате отправления: