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

From Christopher Kings-Lynne
Subject Re: pg_dump: could not parse ACL list
Date
Msg-id 4114A8B9.2010601@familyhealth.com.au
Whole thread Raw
In response to Re: pg_dump: could not parse ACL list  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>$ 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 ...

Yes, phpPgAdmin is currently broken either way methinks.

Chris



pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Re: UNICODE characters above 0x10000
Next
From: Tatsuo Ishii
Date:
Subject: Re: [PATCHES] UNICODE characters above 0x10000