Re: pg_dump: could not parse ACL list - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump: could not parse ACL list
Date
Msg-id 20591.1091812778@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump: could not parse ACL list  (Gaetano Mendola <mendola@bigfoot.com>)
Responses Re: pg_dump: could not parse ACL list  (Joe Conway <mail@joeconway.com>)
Re: pg_dump: could not parse ACL list  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
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 by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Uncommenting .conf WAS: Open items
Next
From: Tom Lane
Date:
Subject: Re: Uncommenting .conf WAS: Open items