Re: pg_dump: could not parse ACL list

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump: could not parse ACL list
Date: 2004-08-06 20:48:51
Message-ID: 4113EEB3.5010308@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Gaetano Mendola <mendola(at)bigfoot(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2004-08-06 22:20:08 Re: Trapping QUERY_CANCELED: yes, no, maybe?
Previous Message Alvaro Herrera 2004-08-06 18:51:11 Re: CVS comment